Keep cached event pages current
Understand automatic cache clearing and what your host still needs to verify.
Supported automatic clearing
MetaSprout requests a site-wide HTML cache purge through an active Nginx Helper or WP Rocket integration after committed imports, public permission changes and published-layout changes. Draft-only layout edits do not trigger a purge.
These integrations are optional. MetaSprout does not require a cache plugin to import or display data.
Follow-up clearing
A follow-up sweep is scheduled for about 60 seconds later to clear older renders that may have been in progress. Actual timing depends on the host's cron runner. Provider exceptions can trigger bounded retries.
Cache failures do not undo an already committed import. A notice distinguishes a purge request, a provider error and the absence of a supported integration. A request alone is not proof that every cache layer was cleared.
What has been verified
xCloud FastCGI with Nginx Helper was tested with caching enabled and without an event-page exclusion. Hidden/deleted presentations, event unpublishing and a published layout change all produced fresh output.
The WP Rocket integration is implemented but has not had the same live-host acceptance test. Independent CDNs, browser caches, multisite and other caching products need separate verification.
If old content remains
Check the page while logged out. Identify every cache layer with the host and confirm the purge integration is active. Unsupported caches may need their own purge automation or exclusions. Do not assume a successful import means an independent CDN has refreshed.
Related: Visibility changes and Troubleshooting.