Testing the automatic upgrade to WordPress 3.0

Testing the automatic upgrade to WordPress 3.0

Are you interested in trying out the automatic upgrade from WordPress MU 2.9.2 to WordPress 3.0 before WordPress 3.0 is released? Currently, WordPress 3.0 is at RC1 and it may be another two weeks or more before it 3.0 is officially released.

Upgrading a WordPress MU install to the WordPress 3.0 RC with the built in upgrade feature is now possible with the WordPress Beta Tester plugin. Here are the steps:

  • Make a backup of your database and files in your MU install
  • Install and activate the latest (0.92) version of the Beta Tester plugin
  • Go to the beta tester admin page under Tools->Beta Testing
  • Choose the Bleeding edge nightlies radio button & Save
  • Click on the head on over and update now link to go to the Update admin page
  • Click on Upgrade Automatically
  • After the upgrade is complete, click on your Dashboard icon

Issues & errors may be reported at WordPress Trac. Note that some themes and plugins may need to be updated to work with WordPress 3.0. Please try to determine whether an issue is plugin/theme related or an issue WordPress. Issues with themes and plugins should be directed to the theme/plugin author.

(Visited 10 times, 1 visits today)
  • Tweets that mention Testing the automatic upgrade to WordPress 3.0 - WPMU Tutorials -- Topsy.com
    Posted at 02:25h, 02 June Reply

    […] This post was mentioned on Twitter by D_time and Denise Sterling, Pete Mall. Pete Mall said: RT @wpmuguru: Testing the automatic upgrade to WordPress 3.0 http://is.gd/cz2hE […]

  • Justin has a nice theme developer orient… « WordPress Development Updates
    Posted at 09:40h, 02 June Reply

    […] talks about upgrading from MU to 3.0. […]

  • Derek Pennycuff
    Posted at 10:43h, 02 June Reply

    Sorry if this is a noob question but does this mean that 3.0 incorporates features you used to have to use MU to get? You’re not talking about going from MU 2.9.2 to MU 3.0, implying that there’s no real need for an MU specific v3.0. Or am I missing something.

    • andrea
      Posted at 11:15h, 02 June Reply

      Yes, we’re talking about going from wpmu 2.9.2 to WordPress 3.0.

      The MU codebase is now merged in with WordPress so there is now only one project going forward. 3.0 fully support what was MU. Users who currently have a single WP install can now enable what was mu functionality.

      This has been know as “the merge” and was announced last year.

      • Derek Pennycuff
        Posted at 14:04h, 02 June Reply

        Thanks Andrea. We may rebuild our blog server over the summer so maybe we should wait for the official release of 3.0 and pretend we never even did anything pre-merge. I’m pretty much our only active user at the moment anyway. 🙂

      • Phyllis
        Posted at 12:31h, 17 June Reply

        so…does that mean…that if I just update WP when 3.0 come out – that I don’t have to download and upload MU right now? Wasn’t it supposed to be already done by the 15th? Do I take the time to download and install MU now – or wait for the 3.0?

  • Demetris
    Posted at 11:46h, 02 June Reply

    Hello, Ron and Andrea!

    Quick question:

    When 3.0 final is released, while the upgrade from MU 2.9.2 require any special steps, or is it expected to be a straighforward affair?

    • Peter Westwood
      Posted at 12:40h, 02 June Reply

      2.9.2 MU will see 3.0 Final as an upgrade yes.

    • Ron
      Posted at 13:30h, 02 June Reply

      By doing this with the beta tester plugin, we are testing the internal upgrade process from MU to WP 3.0.

      Per Peter’s comment – when WP 3.0 is released, MU installs will have the upgrade notice that WordPress 3.0 is available. Upgrading at that point will not require the beta tester plugin.

      • Phyllis
        Posted at 12:33h, 17 June Reply

        so I would already have to have installed MU to get the update notice? Sorry for the noobie question…

    • Demetris
      Posted at 14:02h, 02 June Reply

      Thanks, Peter and Ron!

  • Peter Westwood
    Posted at 12:40h, 02 June Reply

    Great to see WordPress Beta Tester being put to good use again 🙂

    • Ron
      Posted at 13:32h, 02 June Reply

      Yeah 🙂 That was a handy way to do this as well.

  • Gabe Taviano
    Posted at 13:13h, 02 June Reply

    Trying this now on http://wp.riverradio.com (site we are preparing for launch). Would like to upgrade it from WPMU 2.9.2 to WP 3.0, but it appears to be getting stuck on the “Unpacking the update.” step after clicking Upgrade Automatically. Any thoughts?

    • Ben Tremblay
      Posted at 16:06h, 02 June Reply

      @gabe – Going by my experience (see [Plugin: WordPress Beta Tester] FAIL after activation) it might not matter.

      At that step in the process (if I’m not mistaken) you’re updating to WPMU 2.9.2.
      I already had 2.9.2 at that point, but the update proceeded anyhow.
      Unless something has been damaged, I’d say you can proceed with updating to WP3.

      tally ho!

  • Ben Tremblay
    Posted at 14:08h, 02 June Reply

    This ranks right up there on the n00b list!

    I moved to do backup of my WPMU expecting to find it as plop-plop fizz-fizz as with WP.
    No joy?

    Q: PHPMyAdmin as per http://codex.wordpress.org/Backing_Up_Your_Database is the way to go?

    I’ve been waiting a long time for this merge, so will proceed one way or another.
    Just want to confirm this.


    p.s. http://issuepress.com

    • Ben Tremblay
      Posted at 14:34h, 02 June Reply

      I decided to just gun it. (dB is almost empty; just a sketch of things to come.)

      No joy; I’ve lost access to Admin viz,:
      “Fatal error: Call to undefined function register_setting() in /home/.taos/bentrm/issuepress.com/wp-content/plugins/wordpress-beta-tester/wp-beta-tester.php on line 35”

      I’ll head over to the plugin’s homepage. *sigh*

      • Ben Tremblay
        Posted at 15:43h, 02 June Reply

        My bad: I wasn’t running the most recent WPMU.

        So my WPMU site is now running #WP3. I’ll need help with “update your server rewrite rules to use wp-includes/ms-files.php” *gasp!* but it looks like things worked fine. (Pretty confusing at times; upgrade only went as far as 2.9.2, even with Bleeding Edge set, until I did the “click on your Dashboard icon” magic.)

  • Jonathan
    Posted at 11:13h, 03 June Reply

    I install all my WPMU instances from a svn checkout…any idea if running ‘svn switch’ will work for upgrading WPMU 2.9.2 to WP 3.0?

    • andrea
      Posted at 12:43h, 17 June Reply

      I think they’re going to switch the svn on their end.

    • Morten Blaabjerg
      Posted at 16:22h, 19 June Reply

      Apparently, I can’t seem to update to 3.0 smoothly via SVN yet.

      svn sw http://core.svn.wordpress.org/tags/3.0/ .

      Prompts this :

      svn: ‘http://core.svn.wordpress.org/tags/3.0’
      is not the same repository as

      And attempting to checkout over the existing install gives me this :

      svn: ‘.’ is already a working copy for a different URL

      Tried searching for a solution to make this upgrade as smoothly as possible via SVN but have yet to find one.

      Any ideas?

      • Ron
        Posted at 22:16h, 19 June Reply

        You’ll have to check out the WordPress svn. svn switch is for switching to different areas within the same repository.

        • Morten Blaabjerg
          Posted at 03:15h, 20 June Reply

          Thanks, Ron. How should I best checkout wp 3.0?

          I get the “is already a working copy for a different URL” error if I try to checkout wp 3.0 over the existing 2.9.2 wpmu files. Should I simply eradicate the old files and set up wp 3.0 from scratch in a fresh install?

          In that case, do you know what settings I would need to keep and what files I should alter, or would things proceed somewhat smoothly afterall?

      • Morten Blaabjerg
        Posted at 17:10h, 20 June Reply

        Decided to backup everything and wipe the entire old wpmu install and checkout a fresh wp 3.0 via SVN.

        Then I made sure to follow Andrea’s instructions here :


        I added my old wp-config.php and made the adjustments to that file and .htaccess, and I had absolutely none but only the slightest problems (had to update a few plugins and adjust the admin screen to a two-column setup, that’s all).

        Thought I’d check back and report here, in case someone else with a similar problem comes along 🙂

        • Ben Tremblay
          Posted at 17:35h, 20 June Reply

          I wonder what got tangled up?
          Cuz I fumbled mine pretty badly (issuepress.com), not having updated WPMU to 2.9.2 first … but everything pulled through ok.

  • Gouri
    Posted at 13:35h, 09 February Reply

    I haven’t yet tried activating the MU features in any of my WP sites. It requires a code hack or a plugin, is it?

Post A Comment