Fixing templatealias SQL Errors After Updating from Evolution 1.4.5 to 2.0.2

A successful manager update does not always mean the whole site is actually upgraded cleanly. This donor case is a perfect example: the admin side came up, but the public site immediately failed with an SQL error about a missing templatealias column.

SQLSTATE[42S22]: Column not found: 1054 Unknown column 'templatealias'
select `templatealias` from `modx_site_templates` where `id` = 3 limit 1

Errors like this usually mean the codebase and the database schema are out of sync. One part of the application expects a newer schema, while the database is still using an older structure.

What to check first

• Whether the database migrations or upgrade SQL actually completed.
• Whether the site is mixing old files with a partially updated core.
• Whether cached compiled views or stale autoloaded code are still referencing the wrong state.

The durable lesson here is bigger than this one column. When upgrading across major Evolution generations, always validate the full schema, not just whether the manager login works. A green admin screen can hide a broken frontend runtime.

For blog readers, this post is useful because it turns a vague “Parse Error after update” complaint into a real troubleshooting pattern: schema mismatch, partial deploy, or incomplete upgrade steps.