Tagged: W3 Total Cache Troubleshooting
- AuthorPosts
- November 19, 2021 at 8:41 am #45094Brian GoedkenGuest
November 18, 2021
Yesterday my new website was working fine. I am in the process of loading plugins and build content.
Today, as I tried to login into WordPress site, I received an error to the effect that I need to “Cookies for must be Enabled for WordPress”.
I checked in Chrome/Firefox and they were enabled. I also added WordPress to the Always Approved list.
This did not resolve the login error.After this, I only performed the following action to get successfully logged on:
In cPanel File Manager, I renamed the W3 Total Cache folder (temporarily) and then I was able to logon.
I am running WP Version 5.8.2
Could you please check to see what is causing this issue?
If you need additional information, please email me.
Thank you.
November 19, 2021 at 9:54 am #45116Marko VasiljevicKeymasterHello Brian,
Thank you for reaching out and I am sorry about the issue you are experiencing with W3 Total Cache.
This is a very strange issue to be related to W3 Total Cache, and I am not quite sure (the first time I am seeing this kind of issue) what may be causing this.
Potentially, some cookie was cached in the browser or the Page Caching was not disabled for logged-in users.
I would recommend removing the plugin and re-install:
3. Check .htaccess File (make a backup)
W3TC will create many directives in the .htaccess file to control the 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 left over in your .htaccess file after deleting the plugin.
1. Delete wp-content files and folders
– cache folder
– w3tc-config folder
– object-cache.php (if exists)
– advanced-cache.php (if exists)
– db.php (if exists)
– upgrade folder
– delete w3-total-cache folder in wp-content/plugins/ (the folder you renamed)
2. 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 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.
3. Go to your wp dashboard and re-install W3 Total CacheOnce the plugin is re-installed make sure that when you test the behavior after enabling the settings one by one, and make sure that caching is not enabled for logged-in users.
Let me know if this helps!
Thanks!
November 21, 2021 at 3:14 pm #45127Brian GoedkenGuestMarko,
THANK YOU for getting back to me and providing the detailed guidance.
Fortunately, today, I was able to login without issue.
I did not mention, but there were a couple of internet pages that provided a range of options for this issue. So, it is something that has occurred with w3TC before for others.
https://wp-staging.com/how-to-fix-the-error-cookies-are-blocked-or-not-supported-by-your-browser/
How to fix “Cookies are blocked or not supported by your browser” in WordPress
They also suggested a re-install and alternatively some coding in the wp-config.php file —- neither of which I tried.
Is there a way to save all the settings before deleting? It is such a complicated app with so many options and takes a lot of time to properly optimize, especially when many people would be relative novices as setting up W3TC or any cache plugin for that matter. It would be unnerving to start over again.
Anyway, if it happens again, I will refer to your suggestions below.
Thank you!
November 21, 2021 at 3:23 pm #45174Marko VasiljevicKeymasterHello Brian,
Thank you for the information and I am glad everything is working as expected.
Yes, you can backup the settings:
1. Download the .json file in Performance>General Settings, scroll down to Import/Export settings and click on Download to Export Configuration.
2. You can make a backup of wp-content/w3tc-config/master.phpThank you!
- AuthorPosts
- The topic ‘W3 Total Cache Preventing WordPress Login’ is closed to new replies.