Cache not clearing or showing old content
Why visitors still see an old page after an edit with TurboCache, how lazy invalidation works, and how to force a refresh.
First, check what you are looking at
Log out (or use a private window), load the page and read the X-TurboCache-Cache header in your browser’s developer tools:
HIT— served from the cache, current version.STALE— an older copy is being served while the new one is built. This is normal for a short time after an edit.MISS— WordPress built the page just now.BYPASS; reason=…— not cached at all (for examplelogged-in,excluded-uri,woocommerce-dynamic).
Old content for a few minutes after editing
With Lazy invalidation on (the default) visitors keep getting the previous, optimised page until the background queue has rebuilt it. Watch the item on TurboCache → Manage → Processing queue. If edits must show at once, choose Forced updates show original on Cache and revalidation, or re-run the wizard with “Always up-to-date content”.
Old content that never goes away
- The queue is not moving. Run self-diagnostics on the Manage screen. If “asynchronous tasks” fails, your host blocks loopback requests: switch Background mode to WP-Cron, and if your site gets little traffic set up a real cron job for
wp-cron.php. - The queue is paused. Select Resume on the Processing queue.
- The changed page is not a dependent page. Editing a post refreshes the post, front page, archives and term pages by default, not author archives or feeds. Tick more boxes under Dependent pages, or use Revalidate this page from the toolbar.
- A widget, menu or footer changed. Menus and widgets refresh the whole site. A change made directly in the database or by a plugin that bypasses WordPress hooks does not — run Revalidate cache with scope All.
- Another cache sits in front. Cloudflare, Varnish or host caching can keep their own copy. Keep Purge server caches on and add Cloudflare credentials, or select Delete server’s cache (if available).
- Your browser kept it. HTML is sent with
max-age=0, so this is rare, but static CSS and JS are kept for 365 days by the browser cache rules. Changed theme files normally get a new?ver=— unless you turned on Remove ?ver= from static files.
Force a complete refresh
- TurboCache → Manage → Operate, scope All, select Delete cache. Everything is removed now and rebuilt in the background.
- Or from any page: toolbar TurboCache → Delete cache.
The page is never cached
Read the BYPASS reason. Common ones: excluded-uri (paginated URLs, /feed/ and anything containing “sitemap” are excluded by default), excluded-args (any query argument makes a page dynamic unless it is on the Ignored arguments list), excluded-cookie, search, 404, donotcachepage (another plugin set DONOTCACHEPAGE). If the Manage screen says “Page cache drop-in is missing” or that advanced-cache.php belongs to another plugin, see Conflicts.
Did this answer the question? No — open a support request