• Resolved xzistance3

    (@xzistance3)


    I recently upgraded my WP MU site to WP 3.1 Everything seems to be running fine except in the back-end. I have two blogs total and they both respond and work as expected on the front-end. However, when I try to go to the dashboard or any other area in the wp-admin of the secondary site, it takes an abnormal amount of time to load; like, anywhere from 45 seconds to 2 minutes.

    I’ve tried disabling all my plugins, removing the new admin bar, etc., but I’m having no luck. I also tried to automatically upgrade my sites by running the Update Network functionality, but I get this error when I try:

    Warning! Problem updating ... Your server may not be able to connect to sites running on it. Error message: Could not open handle for fopen() to https://mysite.com/secondaryblog/wp-admin/upgrade.php?step=upgrade_db

Viewing 15 replies - 1 through 15 (of 16 total)
  • So you disabled every single plugisn – including network activated ones – and then hit the update network or tried accessing the dashboard of either sub blog?

    Thread Starter xzistance3

    (@xzistance3)

    Yes.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Disable the admin bar. If you have a LOT of blogs, it can sometimes bog things down.

    Also, what is your php memory set to?

    Thread Starter xzistance3

    (@xzistance3)

    I have tried disabling the admin bar; both through the plugin and adding a line to my functions file. And there’s at least 512 MB of php memory. Might even be 1024

    Then check how much memory is allocated to mysql.

    Thread Starter xzistance3

    (@xzistance3)

    I have one additional blog other than the main one on my MU install. So, 2 total blogs. And the DB is on a separate server dedicated for just the DB. I don’t know exactly how much there is, but there’s plenty, promise.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    And the DB is on a separate server dedicated for just the DB.

    That may be it. There may be lag between the two servers.

    Thread Starter xzistance3

    (@xzistance3)

    These two servers have been working together seamlessly for over 2 years, so it’s not that. It’s something in the code or something that changed or didn’t change in the database. Nothing else makes sense. Everything was working perfectly fine until I upgraded to 3.1

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Check if your server was upgraded. There was an apache upgrade that buggered me recently with mod_security changes. It could have changed your PHP, which would affect things.

    And see if you can run some speed checks on the connectivity between your servers. Yeah, I know, it’s worked for 2 years, but I’ll bet you dollars to donuts that WordPress is NOT the only thing that changed, eh? So be open minded to follow each path ??

    If it’s on the wp end, it’s either the sub blogs didn’t get upgraded properly OR a plugin is mucking things up.

    yes, some people sporadically report enabling multisite (in general) slows down the admin area considerably. The exact cause is a big fat ol’ “It depends”.

    Thread Starter xzistance3

    (@xzistance3)

    Is there any way to run a script specifically on each blog in the MU without having it to connect to that Network Update thing?

    I feel like there should be a way to run a file locally and manually or something..

    @ipstenu: I understand what you’re saying, but I know the two servers are talking back and forth very fast. Nothing has changed on that end. We have a few other sites that are hosted on the same platform and they are working just fine. Like I said, it’s ONLY when trying to use the admin of the other microsite. The front-end of that blog works fine and fast, as does everything else.

    Is there any way to run a script specifically on each blog in the MU without having it to connect to that Network Update thing?

    Usually visiting the admin area of that blog fires the same upgrade-if-needed process that Network Update does.

    And right after you visit the admin on site2, go check your error logs.

    Thread Starter xzistance3

    (@xzistance3)

    I figured this out.

    For whatever reason, the network update wasn’t working, but if I went to my secondary blog’s wp-admin/upgrade.php file, it allowed me to update it:

    https://mysite.com/secondaryblog/wp-admin/upgrade.php

    I ran the upgrade from this URL and now the backend admin works fast! w00t!

    I’m having exactly the same problem, 2 blogs on a multisite, frontend fine, backend ridiculously slow.

    Are you saying all I have to do is stick a /upgrade.php on the end and see what happens? I’m not particularly techy so this is all a bit hard to fathom sometimes.

    Cheers

    Yes, do that. It basically forces it.

Viewing 15 replies - 1 through 15 (of 16 total)
  • The topic ‘wp-admin of secondary blogs runs super slow’ is closed to new replies.