Super Cache problems

First, a quick way to tell whether Super Cache is involved at all: turn on Pause caching on Settings → AjaxPress → Cache, clear your browser cache, and check again. If the problem goes away, it’s the cache. Turn Pause caching off again when you’re done.

A page looks out of date

• Theme, menu or widget changes appear on every page but aren’t tied to one post, so they aren’t cleared automatically. Click Purge All.
• One page is out of date: open it while logged in and choose Purge This Page from the cloud icon in the admin bar.
• Changes made by another plugin (prices, stock, events) aren’t seen as edits. Purge the pages, or keep them out of the cache if they change often.

See Purge the cache.

A visitor sees someone else’s content

For example another visitor’s name, a “logged in” menu, or a cart with items. Super Cache already skips logged-in users, shoppers with a cart, and any page that sets a cookie. If personal content still reaches the cache, it’s shown by a plugin in a way that doesn’t set a cookie.

1. Add the page to Pages to never cache.
2. Click Purge All.
3. If the plugin sets its own cookie for signed-in members, a developer can add the cookie’s name with the ajaxpress_cf_bypass_cookies filter. See PHP hooks and filters.

Pages are never cached

Check cache health keeps showing MISS or BYPASS.

• A plugin sets a cookie on every page. Pages that set a cookie are never cached. Open a page in a private window, then look in the browser’s developer tools under Network → (the page) → Response Headers for set-cookie. Consent, A/B testing and some analytics plugins do this. Look in that plugin’s settings for an option to set the cookie only after consent or with JavaScript.
• The page is excluded. Check Pages to never cache, and the Don’t cache this page box on that page.
• Caching is paused. Check the Pause caching switch.

Health check says UNKNOWN

The requests didn’t pass through the cache Worker at all.

• The DNS record isn’t proxied. In Cloudflare, open DNS and make sure your site’s record shows the orange cloud (Proxied), not grey (DNS only).
• The Worker route is missing. Disconnect Super Cache and deploy again.
• You’re testing a different address, such as www.example.com when the route is for example.com/*. Make sure your site address and the Cloudflare route match.

Over the daily Worker allowance

On Cloudflare’s free plan, Workers have a daily allowance of requests. Every request to your site counts, including images, scripts and styles. On a busy site you may pass it.

What happens then depends on the route’s Request limit failure mode in Cloudflare (Workers Routes → edit the route):

• Fail open (proceed): requests skip the Worker and go straight to your server. Your site keeps working, uncached, until the allowance resets.
• Fail closed (block): visitors see a Cloudflare error page.

Set it to Fail open, then consider Cloudflare’s paid Workers plan if you pass the allowance regularly.

“Your site domain is not found in your Cloudflare account”

See Connect Cloudflare.

“Cloudflare rejected the zone for this site”

Shown when purging. The zone Super Cache was set up on no longer matches, for example after the domain was removed and re-added in Cloudflare. Disconnect, then connect and deploy again.

“The edge worker could not be updated after several attempts”

Your site is still cached by the worker already installed, so nothing is broken. Click Update worker now. If it keeps failing, disconnect and deploy again. See Worker updates.

Purge doesn’t seem to work

Use a full address in the purge box, starting with https://. Paths and wildcards such as /blog/* aren’t accepted by Cloudflare. For a whole section, use Purge All.