WordPress MU 2.8.3

WordPress MU is a multi user or multi blog version of WordPress that is used to run sites like WordPress.com.

WordPress MU 2.8.3 is a security and bugfix release based on the fixes in WordPress 2.8.3 but also contains many other changes.

It’s a required upgrade for security reasons but also fixes a number of annoying bugs, especially #1067 and #1076.

Unfortunately the automatic upgrader in MU 2.8.2 is broken but it’s simple to fix:

  • Before upgrading, edit wp-admin/includes/class-wp-upgrader.php and look for line 697.
    if ( !$wp_filesystem->copy($working_dir . ‘/wordpress/wp-admin/includes/update-core.php’, $wp_dir . ‘wp-admin/includes/update-core.php’, true) ) {

  • See the “/wordpress/wp-admin/includes” bit? Change that to “/wordpress-mu/wp-admin/includes”:
    if ( !$wp_filesystem->copy($working_dir . ‘/wordpress-mu/wp-admin/includes/update-core.php’, $wp_dir . ‘wp-admin/includes/update-core.php’, true) ) {

  • Save the file and auto upgrade. I upgraded this afternoon without a hitch after making that change. It’s fixed in 2.8.3 so it’s the last time you’ll have to do it.

Do not copy and paste the line above as WordPress will have changed the quotes to “smart quotes”. Actually go in and type “-mu” after “wordpress”. No copy and pasting please!

If auto upgrading still doesn’t work, don’t sweat it. Download the new release from the download page and upgrade manually, overwriting your current install with the new files.


39 Comments

WordSkill (11 comments.) on August 7, 2009 at 10:12 pm.

Good stuff, thanks Donncha.

Looking forward to next week’s 2.8.4 :)

Reply

mwaterous (9 comments.) on August 8, 2009 at 12:21 am.

Not too far off of what I was thinking myself. ;) They need to make this an aptitude package so I can just upgrade it through cron.

Reply

Dewey on August 8, 2009 at 12:54 am.

Thank you, sir! That promptly ended my hour long mission trying to figure out it kept failing. :)

Reply

Jeremy (5 comments.) on August 8, 2009 at 2:59 am.

In your blog, why not wrap the above code in <code> tags? That will stop it from doing smart quotes.

Reply

Robert (7 comments.) on August 8, 2009 at 3:07 am.

Glad i checked your blog before I hit the upgrade button :)

Reply

Adam W. Warner (1 comments.) on August 8, 2009 at 12:59 pm.

Thanks as always sir, worked like a charm:)

Reply

Seth (1 comments.) on August 8, 2009 at 3:53 pm.

Thanks for the posting the wp-class-upgrader.php fix!

Reply

Jom (1 comments.) on August 8, 2009 at 4:33 pm.

Thanks a bunch. I was able to upgrade my wordpress MU with no sweat.

Reply

Sanjeeva on August 8, 2009 at 4:54 pm.

Great tip. Saved me from lots of trouble. Thanks.

Reply

Mehmet GÜNDOĞDU (1 comments.) on August 8, 2009 at 6:17 pm.

Thank you :) now waiting 2.8.4

Reply

Engelbert on August 8, 2009 at 6:21 pm.

Great help! Thanks for that.

Reply

ZKWC (1 comments.) on August 9, 2009 at 1:43 am.

Thanks for the helpful info! Had no idea why it wasn’t unpacking. ;) That little fix works.

Reply

swingJazz (1 comments.) on August 9, 2009 at 1:51 am.

Thank you very much Donncha.

Reply

ray on August 9, 2009 at 6:56 pm.

little reminder to all code pasters: always remember to check code snippets you are pasting from a website into an editor for tick marks, inverted commas, single quotation marks – because ’ is not ‘ , even when it looks like it on this page.
besides that: the update went through fine, so i must acknowledge that this was a really big mu-ing step!

Reply

Angelo (4 comments.) on August 9, 2009 at 7:32 pm.

I use subversion to upgrade, but the repository at http://svn.automattic.com/wordpress-mu/ doesn’t contain a tag for 2.8.3 now… can you create one or let us know which revision number to use?

Reply

Jeremy (5 comments.) on August 10, 2009 at 12:50 am.

Angelo, the branch at http://svn.automattic.com/wordpress-mu/branches/2.8/ (use svn switch to switch to the branch) will be equivalent for now.

Reply

Angelo (4 comments.) on August 10, 2009 at 1:39 am.

I don’t want to end up with the latest commit on 2.8, I just want releases. Does stuff get commited to the branches in between releases?

Reply

Angelo (4 comments.) on August 10, 2009 at 2:35 am.

Ok, it looks like 2.8.3 is revision 1929 in trac, and looks like the branch isn’t updated yet… so I guess I’ll do that. But I’ll have to remember not to do any updates until the next release.

Reply

Donncha (1707 comments.) on August 10, 2009 at 1:12 pm.

I just tagged 2.8.3 so you can update from that if you like.

Reply

Jeremy (5 comments.) on August 10, 2009 at 1:13 pm.

Yay, thanks!

Reply

Mat_ (1 comments.) on August 10, 2009 at 8:18 am.

Thanks for the tip :)

Reply

Wabber (1 comments.) on August 10, 2009 at 7:04 pm.

Hi.. thanks for the tip.. worked perfectly :) Saved me trying to figure out which files to upload manually.. thanks!

Reply

Mark on August 11, 2009 at 2:22 pm.

Hi,

thanks for the workaround. I just tried it, but I got a warning message saying, that I am trying to download the en-us-Version which doesn’t match with my language version.

So what to do?

Kind Regards
Mark

Reply

kunal on August 12, 2009 at 5:43 am.

Sorry for the newbie question, but I would not see this problem if I was upgrading directly from a version prior to 2.8.2 would I? I am still running 2.7.1

Also, is 2.8.4 expected soon? If so, I might just wait a bit and upgrade directly to that.

Thanks!

Reply

Mark on August 12, 2009 at 9:40 am.

Just found this today:

http://wordpress.org/development/2009/08/2-8-4-security-release/

So we are right now running from update to update … ;)

Reply

Pingback: WordPress MU 2.8.4

Jason Friesen (1 comments.) on August 14, 2009 at 2:00 am.

Perfect—worked a treat. Thanks for the instructions.

Reply

Gaetan on August 14, 2009 at 11:50 am.

Thanks a lot Donncha!

Reply

Mark de Scande (1 comments.) on August 14, 2009 at 9:15 pm.

Thx for the help now to update 24 MU Sites

Bloglines SA

Reply

Leave Your Comment

Your email will not be published or shared. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>


Holy Shmoly! is Stephen Fry proof thanks to caching by WP Super Cache