by andrea

Testers, start your engines

The bulk of the merge has been done in WordPress core. At least with regards to moving over the files. Now the fun part begins: bug gardening, testing and tweaking.

Here’s what you can do to help not only the dev team and others, but also yourself:

– set up a local install of WPMU
– import some data, plugins & themes from your current setup
(in other words, create a working copy somewhere)

Now, upgrade it to the latest WordPress trunk. The zip is located at the bottom of this page. To manually upgrade, just overwrite the MU files with the files located in the zip.

When you find bugs, please file them over at the WordPress trac, and pick the term multisite in the component field dropdown, so the other devs know is it MU related. Some terminology is changing, so this refers to the multiple blog capabilities. Your login to file a ticket is the same as your forum username and password.

Did you get the part where I said to do this on a dev version and not a live site? Good. 🙂



  1. Just got it installed (even did it via SVN), and look forward to playing with it tomorrow

  2. Hey Andrea. Like I posted on Twitter, I wanted to just set up the site from the beginning using SVN into the trunk. You were busy moving beds and stuff, so I just dove in and used:

    svn co .

    Does that get me to the same point as your post or am I missing something by not having installed WPMU first?


  3. Going to have to spend some time learning the trac system so I can be more effective with possible contributions. Massive head/sinus invasion is making that difficult currently. And as I enter an infinite loop when I make the changes spelled out in the Network section to go from SU to MU, I’m going to wait till I think better. It’s possible there’s a challenge with my Nginx setup (and having different regex stuff than the stock .htaccess. But who knows!)

  4. Trac looks scary, but it really isn’t all that bad. I submitted a couple bugs last week, it was very cool to see just how quickly a patch was created and committed.

    Make sure that you document the steps that you take troubleshooting issues, as it may be helpful feedback if there is indeed a bug.

  5. So, I figured out that if I actually read the error message on the Chrome page and deleted my cookies for the trunk enabled site, after applying the Network changes, I don’t get caught in that infinite loop. Sweet, but still major “duh” on my part!

  6. Looks pretty easy…will be giving it a try soon.

Leave a Reply

Your email address will not be published / Required fields are marked *