Hello @gragaer
I am sorry about the issue you are experiencing and I am happy to assist you with this.
Have you tried purging the cache? Also, please delete the /cache/ folder from wp-content manually and see if the issue persists.
Thank you!
Yes, I’ve purged all Caches. I don’t know where this folder is though, somewhere in my installation?
found the folder. error is still the same.
Hello @gragaer
Are you positive that the issue started after updating the Plugin?
I can see that the first post showing is from March 4th.
Try to completely remove W3 Total Cache.
1. Purge Cache
2. Deactivate and Delete Plugin
3. Check .htaccess File (make backup)
W3TC will create many directives in the .htaccess file to control caching behavior. Each section will start and end with comments like “#BEGIN W3TC Page Cache core” and “#END W3TC Page Cache core”.
Ensure that no residual entries are leftover in your .htaccess file after deleting the plugin.
4. Delete wp-content files and folders
– cache folder
– w3tc-config folder
– object-cache.php (if exists)
– advanced-cache.php (if exists)
– dbcache.php (if exists)
– upgrade folder
– delete w3-total-cache folder in wp-content (if exists)
5. Delete Cached Files from CDN (if using CDN)
Besides deleting all the relevant files, if you use CDN then ensure to purge the cached content from your CDN. This is necessary when you enabled the minify option in W3TC settings. You should delete the minified and combined scripts and CSS files from your CDN server to avoid the site breaking on the browser.
If the issue continues to persists after this then it’s not related to W3 Total Cache.
I deleted basically all plugins and reinstalled them again. I don’t know why WordPress sent me the email that W3 Cache causes this error but in reality it was the plugin Jetpack. For some reason the option Infinite Scroll doesn’t work anymore since the latest Jatpack update (which coincided with the W3 update).
So sorry for your hustle but thanks for the support anyways!
Regards,
Ben
Hello @gragaer
Thank you for the information. Glad to know you managed to find the cause of the issue.
Thank you!
