If you’re a WordPress user and happen to use the W3 Total Cache plugin to improve site performance, you might want to hold off upgrading to the new version 0.9.2.6 that just came out this morning. I’m sure W3TC developer Frederick Townes is working on a fix, but this particular version sent two of my domains south this morning. In one case, after upgrading, I got nothing but a 500 internal server error message, while on the other site, I got locked out of the administrative backend by The White Screen of Death.
If you take a look at the plugin’s forum page, you’ll see numerous reports of both types of errors. Below are instructions for how I fixed the problems on both of my sites:
Solving the 505 Error
- Temporarily rename your
.htaccessfile to.htaccess.bk, which should immediately solve the 505 problem, but will disable any other functions in your.htaccess. - Duplicate the backup file, then strip out any lines related to W3TC in the duplicate.
- Rename the duplicate file back to
.htaccess. This should solve your 505 for good.
Solving Admin Lockout
- Disable all plugins by temporarily renaming the
wp-contents/pluginsfolder to something else. - Delete the folder
w3-total-cachewithin the renamedpluginsfolder. - In the root of the
wp-contentsfolder, delete the following:advanced-cache.php



