Troubleshooting

Most Evolution CMS problems come from one of a few predictable places: resource state, template assignment, TV data, parser syntax, cache, or package configuration.

First Checks

1. check the resource: template, alias, parent, published state, cacheable flag
2. check TVs: is the data really saved for this resource and template?
3. check parser syntax: wrong tag names and parameter names are common
4. clear cache after changing templates, chunks, views, or package registration

When Output Looks Wrong

• verify whether the snippet is cached: vs
• verify chunk names, TV names, and placeholder keys
• check whether a plugin changes output during OnWebPagePrerender

When Package Features Fail

• check Composer dependencies
• run package discovery again
• check migrations and published assets
• check routes and service-provider registration

php core/artisan cache:clear-full
php core/artisan package:discover
php core/artisan route:list
php core/artisan migrate:status

When to Isolate Extras

If a problem appeared after installing or updating an extra, disable or isolate that package first. Legacy extras, manager plugins, and parser hooks can all change behavior globally.