Blog Sections Open

Fixing MultiTV SQL Errors After Upgrading an Older Evolution CMS Site

If MultiTV starts throwing SQL parse errors after an upgrade, look first at unresolved placeholders and legacy include paths in the TV configuration.

Upgrade-related MultiTV failures often look dramatic because they surface as SQL syntax errors inside the manager. In many cases the root cause is much simpler: unresolved placeholders such as [+PREFIX+], outdated include files, or old custom TV definitions that no longer match the upgraded runtime.

What to inspect

  • the TV input configuration and included PHP file paths
  • placeholder expansion in SQL fragments
  • whether the custom input file expects an older manager or parser context

After upgrades, custom TVs deserve the same review attention as snippets and plugins. They often carry hidden assumptions from the older build.

Newer post

Fixing E_DEPRECATED Notice Errors After Upgrading from Evolution 1.0.12 to 1.0.13

How to interpret E_DEPRECATED constant errors and header warnings that appear immediately after an Evolution CMS upgrade.

Older post

Fixing File Manager Paths That Resolve to undefined/files Instead of assets/files

How to debug broken manager file paths when non-admin users see undefined file manager roots after an update.