WordPress Dashboard / WP Rocket Settings Page Doesn't Update
It may happen that WordPress backend or WP Rocket Settings Page are not being updated or changes can't be saved as expected. The causes and possible solutions are presented below.
Can't Save / Update WP Rocket Settings
You should be able to toggle settings on and off, and set or remove exclusions as per your needs, by just clicking on the Save Changes button at the bottom of each tab.
However, you might come across a situation where the settings changes are not saved, as shown in this video.
WordPress Dashboard Doesn't Update
You might notice some elements in the dashboard, such as the status of the plugins, are not being updated accordingly after you've applied changes.
Possible causes and solutions
WP Rocket's caching and optimizations don't run in the WordPress backend, so it's highly unlikely that these issues are related to WP Rocket.Usually these cases are related to another layer of caching in the backend:
Object cache such as Redis or Memcached, may be storing queries with WP Rocket settings preferences in your database, and not updating them accordingly.
Either purge the object cache in your server or temporarily disable it. You can also ask your hosting provider to assist you with this.
If you're using Cloudflare's Cache Everything, please make sure to exclude all the /wp-admin URLs as per this guide. The same exclusion should be done for any other cache layer that is active in your admin area.
In that case generally, all plugins are being blocked, not just WP Rocket. Check your server logs and you'll find a lot of
client denied by server configuration errors or a similar message.
You'll need to contact your host support and solve this with them.
3rd party plugins and themes misusing WP Rocket's hooks
WP Rocket has functions to enable/disable features, and filters to process exclusions from our features.
If misused, they can make it seem like specific settings are not updated.
Reach out to our support to help you locate what the conflicting 3rd party asset is. Once found, the issue will need to be resolved on the 3rd party's asset's end.