Turn off minify AND empty the cache. Beware that sometimes it breaks the site ONLY for NON logged in users… for this reason it could take a while before you are notified.
This is what happened in my case. The worst part is that Apache didn’t even log the 500, so I wasnt alerted to it.
well that sucks will they fix it?
I have no logged in users besides me, because i dont have logins, its a news site and a seperate forum no one can login to the wp site.
@a_ahmed, can you please submit a bug submission form from the support tab of the plugin?
The same thing happened for me with the latest update. I thought it was the webhost (and truth is, their support wasn’t good or they would have picked up on the problem) and after three days of downtime I switched to a new host for the first time in two years. We have a busy site and couldn’t risk losing all our readership.
The new host figured out that the issue was coming from the plugin, so in the meantime I have it deactivated. Like those above me, I never saw an issue because it only appeared for those who weren’t logged in.
The problem is that we really rely on the plugin to help with our server load. The plugin is amazing and it helps us leverage memcached, APC, and Amazon Cloudfront. So I really hope this gets ironed out because I don’t want to use WP Super Cache if I don’t have to. That plugin just doesn’t compare to W3 Total Cache.
I had a lot of issues updating w3 cache, but i fix it deactivating the plugin, then update and then activate again.
Don’t sure if this can help you, but for me works fine in a lot of sites.
No uninstalling and reinstalling did not fix it and neither did deactivating and reactivating. In fact uninstalling the whole plugin is what fixed the site lol.. and yes i want the plugin back… it helps alot with performance..
I’m not reinstalling it as my site is live now… and that just sucks to lose users because of site failure…
Can you install the plugin and deactivate each options inside it and activate one by one. If not another thing that you can do is clean the whole w3cache directory with the all files and make a clean and new install of the plugin.
its not solving the issue. This version is messed up and until everyone reports the issue resolved im not reinstalling it my site is live
The frontend of my site is fine. When I try to access the backend, i.e. /wp-admin, I get the following, whether logged in or not:
Warning: require_once(/[path]/wp-content/plugins/w3-total-cache/lib/W3/NewRelicService.php) [function.require-once]: failed to open stream: No such file or directory in /[path]/wp-content/plugins/w3-total-cache/inc/define.php on line 1435
Fatal error: require_once() [function.require]: Failed opening required '[path]/wp-content/plugins/w3-total-cache/lib/W3/NewRelicService.php' (include_path='.:/usr/lib/php:/usr/local/lib/php:/[path]/wp-content/plugins/mailchimp-widget/lib') in /[path]/wp-content/plugins/w3-total-cache/inc/define.php on line 1435
I am deleting the plugin and cache files via FTP as I cannot access the backend at all. I will wait until I hear that it’s working before reinstalling. And I’ll not update the plugin on other sites.
