Divi WordPress Theme

Earlier this week, WordPressMU 2.7 was officially released, and the crowds rejoiced and broke out into song. There’s a whole pile of new things, and if you can’t remember what was new for regular WordPress 2.7, here’s a brief list:

  • brand new admin area redesign with menu down the left side
  • sticky posts!
  • new dashboard features
  • modular write post area
  • quick edit for mass edits on bulk posts
  • reply to comments from admin
  • threaded & paginated comments (if supported in theme)
  • add new media without adding a post

Well, that’s all fair and good, but what about the MU side of things? Anything new there, Andrea, you wonder? Oh plenty of goodies, I say.

  • ViperBond’s admin bar is now included. Personally, I think it’s pretty redundant on the backend, but you can make it show on the front when users are logged in. This makes the mu-admin bar plugin obsolete.
  • Users can add new users directly to their blog. Note the * next to “Add User” on the menu. This will lead you straight to the Site Admin menu where you can turn this option on. Otherwise, users won’t see it.
  • you can add new plugins formt he backend. This is *only* viewable by site admins, and requires ftp details to be typed in. Also, it just searches the official plugin repositpory, and handles regular plugins, not those in the mu-plugins folder.
  • There’s a spot to add an Admin Notice Feed in the dashboard. This came in an earlier version, but I’m noting it now.
  • In the new config file, there’s a few choice things you can now define. Give it a read, see what you can see. 😀 Looking at trac, some have been there since August, but not many people have noticed.
  • While it doesn’t work from the beta version, the auto-upgrade is *supposed* to work from 2.7 on, so you can upgrade MU automatically from the backend.

So, what’s the catch, then? Well none, really, but from poking around, here’s some issues you may encounter when you upgrade.

  • if using bbpress or buddypress, you’ll have to upgrade those too
  • multi-db from WPMUdev premium hasn’t been updated yet, so wait for that
  • there’s a few new trac tickets in case you want to wait
  • the upper left admin link on ViperBond’s menu bar doesn’t switch between blogs well enough

How to upgrade to 2.7 – easy enough, just keep your .htaccess & wp-config.php file, as well as the entire wp-content directory and sub-directories. Blow away all the rest. Upload the new fresh files. Compare the wp-config-sample.php with your own config file and add any new lines.

Yes, you can just overwrite the old files, but some ftp program and/or servers are a bit sketchy about it and it may not fully take. Trying to troubleshoot an error that was ultimately caused by one small file not getting updated is not my idea of a good time and I’m suggesting you may not like it either. 🙂

If you are upgrading from a version previous to 1.5, I suggest you upgrade to that version *first*, then work out any kinks and continue on. Version 1.5 has the “old” new redesign (light blue with orange), and if you can spare your users having to see two admin area iterations, it helps. One big thing to note if upgrading from that far back, is the versioning jumps from 1.5 to 2.6 to line up version numbers and have less confusion. For more details, check the Codex on Upgrading WPMU. (Find any issues with that? Let me know, I’ll fix it.)


  1. Thanks Andrea,

    This will be the first WPMU upgrade I do with live sites, so thanks for the reassuring upgrade instructions at the end of the post!

    WP single user has a maintenance plugin which will temporarily show a message while activated. It seems just the thing when deleting and uploading core files on a slow connection like mine. (Sometimes it’ll take an hour or more to upload WP core.) Does WPMU have a similar function? I guess it’ll be made redundant with auto-upgrades now.

  2. Thanks for the prompt reply and good ideas.

    Unzipping on the server is a great idea. (Moron me, not to think of it before.) I’ll have to polish up my mad comand-line skilzzz. 🙂

  3. Thanks for the heads-up! My co-workers and I spent last week experimenting with the beta, and decided it was a big enough jump forward that we’d run with it for our spring semester pilot of MU. I’m very glad to know I can go forward with an official release.

    On a related-but-unrelated note, do you have any write-ups on the best way to enable SSL login and admin pages while operating in directory mode in 2.7? (as opposed to subdomains?)

    I’ve tried Admin-SSL, but I’ve been having some problems with 403 page not found errors. It worked with the main blog but not the daughters. I suspect some more mod_rewrite experimentation is needed on my part to get it working properly.

    I also tried using the FORCE_SSL_LOGIN and FORCE_SSL_ADMIN config flags, but again, I ran into problems with the daughters and 403 errors. I plan on revisiting it with fresh eyes on Sunday, so hopefully I’ll find something I missed last week. 🙂

  4. Hi andrea,
    yesterday i have upgraded my WPMU installation on Goelji.com. i was logged in at that time but, since morning i am facing some crazy problems.
    1. the login page is not working.
    2. the logo above login form is pointing to a invalid web address.
    3. the signup page is not showing up.

    Please can you help me out

  5. Thanks for the heads up. I just set up my first WPMU site in the automotive niche and haven’t “opened the doors” yet so I’ll upgrade first rather than screwing up others data if 2.7 seems stable. Also, I dropped a link to this post in a big IM forum.

  6. I figured out my issue, which had nothing to do with WPMU 2.7 OR Admin-SSL; the issue was that ssl.conf’s AllowOverride instruction was set to “none” rather than “FileInfo Options”.

    Many thanks for your “Installing WordPress MU” ebook; in it you reference issues with blogs in subdirectories not loading because of this configuration issue in httpd.conf; naturally, the same thing happens to SSL-protected pages if you’ve set “AllowOverride None” in ssl.conf

    “Obvious” in hindsight of course. 🙂