Blog Sections Open
Generating sitemap.xml for Large Evolution CMS Sites Without Timing Out
How to handle sitemap generation when a large Evolution CMS site outgrows the one-request export model.
A sitemap that works on a small site can become a serious performance problem on a large one. In the reported case, generating sitemap.xml for roughly 25,000 resources hit the PHP execution limit and failed inside the Evolution parser.
That is a sign the export model is too heavy for one request, not that sitemaps are a bad idea. The fix is usually architectural:
- split the sitemap into multiple files;
- generate it in batches;
- or move sitemap building to a scheduled task instead of rendering it live.
On large Evolution CMS installations, sitemap generation should be treated like an export job, not a lightweight page render. Once it crosses that boundary, cron-based generation and segmented sitemap indexes become the safer path.
Improving phpThumb Cache Paths and Remote URL Handling in Evolution CMS
A safer phpThumb pattern for cleaner cache paths, remote images, and more predictable generated filenames in Evolution CMS.
Choosing Between Real Cron and AJAX Cron in Evolution CMS
How to decide whether a scheduled task should run through system cron or an AJAX-triggered pseudo-cron approach in Evolution CMS.