anybody there to help me with this?
Increasing memory limit did it 🙂
That would generally do it, but the source of the problem would likely be a bloated or poorly tested plugin. I have had the same problem with several “large” plugins, and plugin “frameworks”, all of which shipped with so much bloated code and functionality that it easily broke a shared server memory limit.
getting same error, even i tried with fresh installation with old wp version, but got same problem, also tried to increase php memory, but still problem remain, any solution?
how much you increased? i mean memory limit?
I’m having the same problem on my VPS. New installations of 3.6 throw fatal errors when trying to install/update any plugins & themes. 3.5.2 works perfectly fine, but if I update it to 3.6 the same problem occurs.
I’m running Apache 2.4.6 with PHP 5.4.17 on suPHP mode (suEXEC is on).
I temporarily increased the php memory execution limit to 1024M to no avail.
Any ideas?
Hope this helps someone else. I just fixed this on my own VPS
http://wordpress.org/support/topic/cant-install-or-update-plugins-1?replies=2
It appears the problem is Apache 2.4.6. Could be 2.4.6 combined with PHP 5.4 but I doubt it.
I rolled back apache 2.4 to apache 2.2 with PHP 5.4.17 using easyapache and this fixed everything for me.
Certainly probably worth a bug report somewhere to someone but not sure who.
I would prefer to be on apache 2.4 but can live with 2.2 as I would prefer the more recent php build
Hi dannymh,
I rolled back to apache 2.2, as you suggested, and it seemed to work initially when I installed a plugin and all went fine. When I tried to install another plugin, the fatal errors returned.
I reproduced that in two separate cpanel accounts, where in both cases only the first plugin installation worked. Consequent attempts return fatal errors.
It’s very odd!
Turns out the problem was not Apache’s version of available ram. I had EAccelerator enabled in EasyApache and it somehow conflicted with suPHP (that explains why installs worked only the first time, caching was causing issues). I disabled it, rebuilt apache 2.4 and now everything works fine 🙂
same was happened with me I was about to tell you to remove eAccelerator, also Suhosin is also not working properly with the PHP 5.4 if you check your error_log you might notice that too, so better remove that also until its fully compatible.
-Regards.
Awesome I will think about removing eacc for now
Can confirm this is the case. Disabled eaccelerator and put Apache 2.4 back in place and all works again now.
Interesting.
