There are upcoming maintenance events which may impact our services. Learn more

When not logged in my website is showing an old version of the site Print

  • 2

Problem Description

  1. When you're logged in to the WordPress admin your website shows the latest changes, however when not logged in, visiting the website results in an old version of the site where none of your recent changes are showing.
  2. You have double and triple checked that you have cleared your browser cache and you've tried a completely different browser with the same result.
  3. You have a caching plugin installed but it's not activated (or wasn't during testing).

Problem Resolution

We use custom nginx cache detection rules that detect when your site is using a common caching plugin and automatically serves the cache files directly with nginx. This improves performance by avoiding the cascade: nginx -> apache -> php, often resulting in excellent initial server response times between 30ms and 120ms.

If you deactivate a caching plugin and fail to clear the cache files prior to doing so, then leave it installed, our detection rules will continue to serve the cache files. To resolve this complete these steps in exactly the following order. Missing a step or completing them in the wrong order will render the issue unresolved.

  1. If your caching plugin is currently deactivated, reactivate the caching plugin
  2. Use the plugin's option to clear the cache
  3. Deactivate and remove all caching plugins that you have installed.
  4. Use your control panel's file manager or FTP and visit wp-content/cache/ and remove everything within the cache folder (but not the cache folder itself).
  5. If your site is not a development/staging site then reactivate the caching plugin you'd prefer to use (pick only 1). For our recommendations, here's our guide to using caching plugins with WordPress.
  6. Clear your browser cache and load the site again.

Issue should now be fixed.

In the future, we're hoping that cache plugin developers will auto-remove their cache folder whenever their plugin is disabled, which will make this a non-issue.


Was this answer helpful?

← Back