Fixing Old URLs That Persist After Changing Resource Aliases

A confusing alias issue appears when menus and generated source code already show the new URL, but the actual click still resolves to the old alias or the old .html version. That usually means the project is serving stale routing information from one of several cache layers.

What to check

1. clear the Evolution CMS cache fully, not just the visible manager cache
2. check whether the old URL is hard-coded in menus, chunks, or custom snippets
3. review rewrite rules and redirect fragments in .htaccess
4. look for browser or proxy caching if the old redirect persists across requests

Why source and behavior can disagree

The menu source may be freshly generated while the browser still follows a cached redirect, or a rewrite rule may normalize requests toward the outdated pattern. That is why this issue often feels inconsistent: the markup looks fixed, but the request flow is not.

In practice, always test alias changes with a full cache clear and a clean browser session before assuming the CMS still stores the old value.