Refreshing Friendly URLs After Applying Translit Aliases

After generating aliases with Translit, existing resources may still need to be re-saved or rebuilt before the new friendly URLs start resolving correctly.

Installing a transliteration helper does not automatically guarantee that all existing resource URLs are rebuilt the way you expect. If old resources still return 404 after aliases were generated, the site usually needs a proper refresh cycle.

Typical fix path

confirm that aliases were actually written to the resources
clear site cache
re-save affected resources if needed
verify your friendly URL configuration and rewrite rules

Recommendation

Alias migration is not only about generating slugs. It also includes cache refresh, route validation, and confirming that the rewrite layer matches the new URL structure.

Newer post

What to Check First During a Mass Hack of Legacy MODX Sites

When many old MODX or Evolution sites show injected links at once, treat it as a platform-wide incident: audit versions, entry points, and writeable paths immediately.

Older post

Why AjaxSearch Works Only While You Are Logged Into the Manager

If AjaxSearch works only for authenticated managers, the issue is usually routing or access context, not the search logic itself.