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.

[Post to Twitter] Tweet This Post 


bookmark bookmark bookmark bookmark bookmark bookmark bookmark bookmark bookmark bookmark bookmark bookmark
tabs-top  banner ad


27 Responses to “Testing the automatic upgrade to WordPress 3.0”

  1. [...] 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 [...]

  2. 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.

  3. Demetris says:

    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?

  4. Great to see WordPress Beta Tester being put to good use again :-)

  5. Gabe Taviano says:

    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?

  6. Ben Tremblay
    Twitter: bentrem
    says:

    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.

    TIA
    @bentrem

    p.s. http://issuepress.com

    • Ben Tremblay
      Twitter: bentrem
      says:

      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
        Twitter: bentrem
        says:

        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.)

  7. Jonathan says:

    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
      Twitter: andrea_r
      says:

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

    • Morten Blaabjerg
      Twitter: mblaa
      says:

      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
      ‘http://svn.automattic.com/wordpress-mu’

      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 says:

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

        • Morten Blaabjerg
          Twitter: mblaa
          says:

          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
        Twitter: mblaa
        says:

        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 :

        http://wpmututorials.com/how-to/upgrading-from-wpmu-to-wp-3-0/

        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 :-)

Leave a Reply

*
To prove you're a person (not a spam script), type the security word shown in the picture.
Anti-Spam Image