Fixing Hash-Like 404 URLs After Updating from Evolution 1.4.11 to 1.4.12

One of the last unresolved donors from the old archive was extremely short, but the failure mode it described is memorable enough to preserve. After updating from Evolution CMS 1.4.11 to 1.4.12, the site began producing a broken URL that looked more like a hash than a normal alias, and every request ended in a 404.

domen.com/ea935321689f82c52cebc02bdfcd433d

When an update suddenly turns readable page URLs into opaque strings like this, the real issue is usually not content. It is almost always a mismatch somewhere in the routing layer, cache state, or alias generation logic.

What to inspect first

• Friendly URL configuration and rewrite rules after the update.
• Whether old cache files are still serving stale route information.
• Any plugin, extender, or custom alias logic that may still expect the older runtime.

This donor is small, but it documents an important upgrade lesson: if the URL itself becomes unreadable immediately after an update, investigate the routing state before assuming that resources are missing or corrupted.