Blog Sections Open
Clearing the Evolution CMS Cache Through the API or Cron
A safe way to trigger cache refresh from an external PHP file, scheduled task, or deployment script.
Sometimes cache refresh has to happen outside the manager: after a cron import, a deployment step, or a batch content update. In that case the most reliable approach is to bootstrap Evolution CMS correctly and call the cache refresh through the API rather than deleting files blindly.
Why This Is Better Than Manual Deletion
- the CMS stays responsible for its own cache structure
- project automation becomes more predictable
- deployment and import scripts stay easier to maintain
If you automate cache clearing, keep it targeted and intentional. Blind full-cache deletion after every small action usually creates more load than it solves.
Cleaning Up Repeated .htaccess Malware Infections
How to respond when malicious rewrite rules keep reappearing in <code>.htaccess</code> and simple file cleanup is not enough.
Fixing a YAMS Language Switcher That Fails Only in Firefox
Why YAMS may switch languages correctly in most browsers but fail on the home page in Firefox, and how to trace the mismatch.