You need to increase the memory limit in your php.ini file. It’s normally set to 32mb. depending on the type of host you have try upping the RAM to 100mb.
I can load the page without this plugin enabled so you’re saying that I need to up the setting (currently 240mb on 768mb RAM server) to make it load with this plugin enabled?
I don’t see why W3TC should be causing the problem, other than that you might be minifying or caching a plugin that is causing a problem. Try disabling all plugins and then see if the problem goes away. Then re-enable one plugin at a time, hopefully you can find the cause.
I upped it to 400 and still no luck. Maybe there is a setting in W3 Total Cache plugin files that is overriding my Apache php.ini settings?
Disabled all other plugins and no change. I discovered the 256mb memory limit in wp-admin which corresponds to the error message above. The only solutions are to optimize the query, increase the wp-admin memory limit or use a different caching plugin. Two of those require modifying the core code but I think it’s ok where it’s just a small backend tweak. I think that’s less of a hassle than finding another plugin that works like super cache, caches db queries and utilizes APC like this one does and configuring it.
I had the same issue upon installing the plugin.
So I had already installed the plug-in on one site and that went just fine.
Yesterday I installed the w3 total cache plugin on a different site and pressed activate, I then couldn’t reach wp=admin but got the ‘Fatal error: Allowed memory size’ error.
Increasing the memory available in wp-config fixed the issue but it’s definetely and issue with this plugin and probably a cross-interaction with other plugings
For me, I have 36,000 posts in one of my custom post types and WordPress was loading them all at once. By saving a bookmark to my bookmarks toolbar with a search result (so that I don’t have to click to the post type main edit screen), I don’t have the problem anymore.
W3TC doesn’t appear to be able to handle massive admin requests.
And WordPress doesn’t appear to be able to handle massive post tables.
The next release has ~70% memory savings to help people get started easier.
