New to the community? Start here

12k blogs upgrade 3.0.5 to WP 3.2 do you disable mu-plugins?

Hello,

I tried my luck at upgrading to 3.2 from 3.0.5

Took the site offline and uploaded the new wordpress files.

The result was a total flake out. I restored the restored the site so I am not in dire straights but I am still strategizing attempt 2 :slight_smile:

I am not sure what the recommended procedure is in relation to MU plugins. Do you delete them?

Some of them like multi-db and multi-domain are required for our sites to work.

If I disable regular plugins from the main site it does not turn them off for all the sites. So are you supposed to delete the plugin files completely?

I have about 12k blogs.. ugh.

Thu, 7 Jul 2011 18:01:27

Mason
- DEV MAN’s Sidekick
- 2,100 pts: Hero points 9,660 pts: Rep. points LEVEL 27
Ugh indeed!

That’s not great. My hunch is that there may be several plugins that aren’t compatible. Almost every single one of our plugins had to be upgraded for 3.0 and then again for 3.1. Make sure you’ve got up-to-date versions of all of those.

You could try changing the name of the mu-plugins folder so that they plugins are all deactivated and seeing if the install works without them. If it does, add the plugins back to mu-plugins one at a time.

What error did you get anyway? Anything in the error logs?

Thanks!
jozwikjp
- The Incredible Code Injector
- 213 pts: Hero points 288 pts: Rep. points LEVEL 5
Hi Mason,

I pretty much just got a blank page. I was getting the too many redirects error. I have read a couple other places about upgrading to 3.1 + causing a permalink issue.

But I didn’t spend too much time debugging it..

I was in fantasy mode I think.. Magically wanting to will it to work.. :slight_smile:

It appears that if you remove the plugin files under the /plugins folder it disables the plugin but when you reinstate it enables the plugin automatically. Or that is what it seemed to do. So I don’t have to worry about 12k blogs having their plugins messed up.

Do you think I have a better chance of upgrading to latest 3.1 WordPress?

Next upgrade attempt will be in the middle of the night when only my chinese sploggers are using the site :slight_smile:

Some notes

-Duh, at least test run the upgrade on your test install first. Saving 30 minutes and installing the updates without testing will always guarantee hours more down time in restoring databases :slight_smile:

-Come up with a spiffy “network is down, it is because we are doing stuff you will love”

-backup your databases right before :slight_smile: easy one.. My 12k blogs and 256 databases took about 20 minutes to restore 3GB total. Only bad part about restoring a couple times is that the binary log for the slave gets crazy huge.

-Stop any mysql slaves before you upgrade. That way you have a active working copy in case you need to switch DB servers.

-sync wordpress folder, minus the user uploaded content folders somewhere local so it can be quickly moved when it breaks.

-Disable apc caching and wordpress cache.

-Change your header cache expiration. Otherwise css files from your failed upgrade will make your site look bad.
Mason
- DEV MAN’s Sidekick
- 2,100 pts: Hero points 9,660 pts: Rep. points LEVEL 27
Hiya,

Do you think I have a better chance of upgrading to latest 3.1 WordPress?

Wouldn’t hurt to try it. Going from 3.0.x to 3.1.x is where the biggest potential for a problem exists. I’d do it i the middle of the night like you say and give yourself more time to handle any issues that come up.

Of course, you’ll also want to make sure all plugins/theme are compatible with the update. I personally wait till a .3 or .4 release before updating ( so like 3.2.3) just to make sure all the bugs are worked out. Also updating my live sites is one of my least favorite activities :stuck_out_tongue:

If you just change the name of the plugins folder, this will be alright as long as someone doesn’t actually visit their plugins page. Doing this checks for active plugins and will disable everything – again doing it in the middle of the night for your bloggers will lower the odds of this one. You can also throw a maintenance page up for everyone so that no one logs in accidentally.

Good luck to ya. Let us know how it goes!
Shawn
- The Crimson Coder
- 671 pts: Hero points 624 pts: Rep. points LEVEL 6
I agree with Mason – 3.1 was the headache upgrade. A LOT of functionality changed and it really caused a lot of problems.

Yes, use a temp/test installation to work through issues, but for smaller installations, or before you go live, you can use a cookie to help minimize external access to the site while you make it go. Here’s an example that should work with current installations:
```
RewriteCond %{HTTP_COOKIE} !wp-settings-1=%

RewriteRule . http://www.example.com/maintenance/ [R=302,L]
```
However, you should assign a custom cookie and htaccess check to prevent evildoers from exploiting it (however unlikely).