Fixing Blank Pages After Scheduled Unpublish Events with Cache Enabled

One frustrating caching edge case in older Evolution CMS sites appears when documents are unpublished by schedule. Instead of serving the expected next state, the system can hand back an empty page until the cache is cleared manually.

Why this happens

The resource state changes, but the cached representation does not get invalidated the way the project expects. The result is a stale or incomplete cached version that survives until a manual refresh.

What to do

• review how scheduled publish and unpublish events interact with the cache extender or custom caching logic
• make sure the affected resource and any listing pages are invalidated together
• avoid custom output caching that ignores publication state transitions
• test scheduled changes on a staging copy with caching enabled, not only in uncached debug mode

If clearing the cache immediately fixes the page, you are not looking at a content bug. You are looking at invalidation logic that needs to become more explicit.