Zinn® Cache: WordPress cache troubleshooting

WordPress cache troubleshooting

The common reasons a page is not cached, shows old content or breaks after optimisation — and how to find which one you have.

1. The status panel says the page cache is not active — On LiteSpeed the server's cache must be enabled; ask your host. If nginx, Varnish or Apache caches pages in front of WordPress, Zinn® Cache leaves page caching to it and purges it — the Status tab says which. On any other server the plugin installs its own file cache the first time you open its settings as an administrator — open them once, and check that wp-content is writable.
2. Every response says miss — Make sure you are signed out and have no cart or session cookies, then check the Exclusions tab and any query parameter in the address. A unique query string is cached separately.
3. A page shows old content — Something changed outside WordPress, so nothing triggered a purge. Purge that page or everything, and check whether your browser is holding its own copy.
4. Something broke after a Pro optimisation — Turn the last Zinn® Cache Pro option you changed back off. If the page recovers, add the file or script responsible to that option's list of files to leave alone.
5. Two page caches are active — Deactivate every page-cache plugin but Zinn® Cache. Zinn® Cache Pro is not a second page cache; it builds on the free plugin, so keep both.
6. Ask us — Both plugins can prepare a support report. You see the exact contents first, with credentials removed, and nothing is sent until you press send.

With screenshots: https://zinncache.com/kb/wordpress-cache-troubleshooting