Blog Sections Open
Keeping Evo-Style Friendly URLs When Aliases Are Missing
A URL strategy note for projects that want aliases where available but still fall back to numeric IDs, especially after importing older content.
When older content is imported into Evolution CMS, not every resource arrives with a clean alias. Some teams prefer to keep the familiar Evolution-style behavior: use the alias when it exists, otherwise fall back to the document ID.
Why this matters
- legacy imported links keep working more predictably
- you avoid forced transliterated slugs for every imported resource
- nested URLs can still stay readable enough
The practical takeaway
This is not only about aesthetics. It is also about migration safety. When a site has years of ID-based content URLs in the wild, keeping that fallback can be less risky than inventing new slugs everywhere and relying on a large redirect map.
Understanding the index-ajax.php LFI Risk in Legacy Evolution CMS
A security-oriented legacy note on why index-ajax.php was risky, how local file inclusion could happen, and why inherited projects should review this area carefully.
Fixing Strict URLs When Alias Replacements Touch the Wrong Links
A troubleshooting note for legacy Strict URLs behavior where broad regex replacement can accidentally rewrite unrelated links.