• I’m running WordPress 2.7 (now 2.7.1) on a virtual server with PHP 4.4.9 and MySQL 5.0.67

    With any plugins other than the two default plugins (hello.php, akismet) the plugins page does not load but times out with the error “server unexpectedly dropped the connection’ (on Safari) and a blank page (on Firefox). If I delete the new plugin, plugins.php then loads normally. However, plugins-install.php does not work at all. It loads part of the page and then stalls.

    I have this problem with other existing WordPress installations on the same server (each under different virtual servers by domain). I also did a fresh install for a new client with WordPress 2.7.1 and in that case, the problem was slightly different in that it didn’t matter what plugin was in the plugins folder — the plugins.php page refused to load. Even the default plugins broke the page.

    I solved the problem with the new installation by moving the entire site to a different server where everything worked fine. This makes me suspect the server. The server that works is running PHP 4.4.8 and MySQL 5.0.45 which is slightly earlier than the server with the WordPress problems. Both are PSEK servers.

    Has anyone successfully debugged this problem? It started for me when our hosting provider did one of their unnanounced server upgrades in December 2008. At that point, both my older WordPress sites broke (white pages) and only were restored by upgrading from 2.6 to 2.7. The plugins worked when I upgraded the sites at that time, but are now broken two months later despite no further changes on my end.

    So today I tried upgrading to 2.7.1. I did so, and as long as the plugins in the plugins folder were just the default plugins, plugins.php loaded fine. When I added NextGen to the plugins folder, the plugins.php times out as above. And if I delete NextGen, plugins.php loads again. I’ve tried this with two other plugins, and all are on WP’s compatibility approved list for WP 2.7.

    I hate to go to all the bother of moving these sites to the other server, esp when i don’t know what server issues caused the problem to begin with. Some insight about what might be causing the problem and how to solve it, would be much appreciated.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Do you have a choice to run php 5.x.x ?
    Would work better for sure.

    Thread Starter BrattDev

    (@brattdev)

    Thanks for the reply. Regarding php 5, I was wondering whether or not that would be a plus. I’ve found conflicting reports on what version of php is best with WordPress 2.7 and it seemed like most people were saying php 4.

    So you think if I got my server people to upgrade to php 5, that would help? The odd thing is, the server where WP works is running an earlier version of php 4 than the one where WP breaks. Very mysterious.

    Thread Starter BrattDev

    (@brattdev)

    Here’s another question that’s been bothering me — what does it mean if there’s a number (in a red circle) next to the Plugins link in the admin sidebar menu? On the site I am working on, there is a numeral 1 next to Plugins in the sidebar nav. Other WordPress sites don’t have any numbers showing next to Plugins. Just curious since the number doesn’t seem to correlate to anything that I can see. Any ideas?

    Thread Starter BrattDev

    (@brattdev)

    Interestingly, I noticed that I got the same error (Server timed out) on a page on a completely different site (not even a wordpress site) that tries to load an image from the url rather than the path. I wonder what the plugins.php page is trying to do that the server doesn’t like?

    Upgrading to PHP 5 is tempting but I have over 40 sites running on that server and I don’t want to spend the next few weeks cleaning up all the minor glitches that will likely occur if I do that. You kind of want to be ready for a major upgrade.

    So I continue to ponder my dilemma and wonder why it is that when WordPress users encounter the “white screen of death”, those issues never seem to be resolved (or at least, the resolutions are not posted online anywhere). They just fade away. One assumes the people having the white page problems either switch servers, blogging platforms or solve the problem another way, without telling the online community how they did it. ??

    Exact same problem with my wordpress ?? Don’t know what to do…

    Thread Starter BrattDev

    (@brattdev)

    After today, I think I’ve tried everything. I’ve looked at stray line breaks and memory limit and bad paths and permissions, and if anything, it’s slightly more broken (before, I was able to get plugins.php to load with Akismet and Hello.php in the folder — not anymore).

    My solution, which I don’t like, is to migrate the site from the PHP 4.4.9 server to the PHP 4.4.8 server, which seems backward but that’s what works. I would love to know what’s different between the two but looking at phpinfo(), I see nothing. When I have the money, I’ll get a server running PHP 5 and we’ll see if it works. But not this week.

    The troublesome thing for me is not knowing just what broke it. Without knowing that, I feel more reluctant now to recommend WordPress to clients, even though I love it when it works. But I’ve had too many white screens of death problems to want to recommend it except to lone bloggers and very small non-profits — and then, only with full warning about what it entails.

    Anyway, it’s been entertaining reading people’s variously solved and unsolved tales of woe. I do think the white screen of death (WSD) is a major flaw and should be resolved somehow — or a list of more precise server requirements published (which if it exists, I couldn’t find). What does WordPress want! ??

    Thread Starter BrattDev

    (@brattdev)

    PS I figured out what the number next to Plugins in the sidebar means — it was an un-updated plugin. That said, removing the plugin didn’t solve the problem. I still had to remove all the plugins….

    It’s an out of memory problem. PHP5 has a memory limit. Up the memory limit by adding the below line to the very top of your site’s root .htaccess file to resolve this problem.

    php_value memory_limit 1000M

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Trouble Loading Plugins.php In WordPress 2.7 and up’ is closed to new replies.