WordPress MU 2.7.1

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

This release of WordPress MU has been much delayed but I think it’s been worth the wait. Included in this release are a number of new features and many bugfixes. Get it from the MU download page.

Update! In the final rush to get this post written I neglected to add that this release fixes a vulnerability in the importer system that would allow an untrusted user to run PHP code. Thanks to Alexander Concha for discovering the vulnerability and to Barry Abrahamson who recognised that some servers treat unknown file types as PHP scripts.
One more reason to upgrade.

New features and changes include:

  • A revamped plugin system thanks to Andy Peatling. Plugins installed in the plugins directory rather than mu-plugins can be activated and deactivated on all blogs with one click.
  • The admin bar was removed. It’ll be stuffed into a plugin instead. Must talk to Viper007Bond about that.
  • A new “My Blogs” page where a user’s blogs are listed and personal “per blog” settings can be configured. It’s empty right now but it’s easy to add settings to it via plugins. Imagine having a different “Display Name” on each blog you write on! See SetupMenu and HandleFormPOST in the just removed admin bar for example code. That code uses actions rather than filters but it’ll get you started.
  • The site admin can now set a Global Dashboard blog for users who don’t have blogs. Those users will be added to this blog rather than the main blog. The default role of users on that blog can also be set but if they’re not “Subscribers” they won’t be moved if you change the Global Dashboard.

They’re the major changes. Smaller changes include notification of failed blog upgrades [1728], MU will now ignore free space checks when importing posts [1725] and lots more. Check out the timeline for further details.

If you’re running WordPress MU 2.7 you can upgrade from inside the Dashboard. The system will notice that a new version is out and will lead you through the upgrade process, just like in regular WordPress. Plugins can be updated as well through the familiar plugin upgrade process as long as your plugins are hosted on the WordPress.org Plugins Database.

As always this release would not have been possible without the help and encouragement of many people along the way. I know I’ll leave out someone if I try to list everyone but I appreciate all the help people give working through tickets, and helping on the forums.

PS. WP Super Cache was updated today too. New features include an option to stop caching for logged in users, it doesn’t cache previewed posts, and it displays cache size summary information on the admin page now.
PPS. Happy birthday Adam! 2 today and Dad’s finally getting away from the computer now! :)


You might also like

If you like this post then please subscribe to my full RSS feed. You can also click here to subscribe by email. There are also my fabulous photos to explore too!

Published by

Donncha

Donncha Ó Caoimh is a software developer at Automattic and WordPress plugin developer. He posts photos at In Photos and can also be found on Google+ and Twitter.

37 thoughts on “WordPress MU 2.7.1”


  1. Thanks so much for all your hard work on this. I just installed the beta version of 2.7.1 this morning. It was funny to see this released on the same day I installed the beta. Good stuff!


  2. Thanks for the new release Donncha! I turned on the new to turn off caching for logged in users then updated the status. Now when I go to turn caching back on for logged in users, the checkbox stays checked after updating status.


  3. I recently switched to WPMU 2.7 and made changes to core to get desired functionality.
    So I am little skeptical about upgrade as of now but I will surely check use it on a test blog.
    Thanks Donncha for WPMU as it made my life easier than I ever imagined. :-)

    Lots of birthday wishes to Adam. :-)


  4. Yeah, my admin bar makes a lot more sense as a plugin, even if it’s bundled.

    Oh, and I’m more than happy to open up SVN access to my plugin and even start using the Plugin Trac if there’s desire.


    1. Please do. I’d like to package and ship it in Fedora; holding off on reving wpmu there, as the admin bar is a pretty key nav feature for us.

      Unless there’s an easier way for a user to switch amongst their blogs?


  5. Hi Donncha,

    After complaining so much about the delay (I know I am usually too impatient), it would be unfair if I did not CONGRATULATE you and THANK you for this release !

    Alex


  6. Love your plugin! Right now I’m not seeing my comments when I comment on my own blog. So if I comment (while logged in) I don’t see comments I just made unless I delete the cache. Any ideas?


  7. I upgraded, but when I turn it on I don’t see comments when I comment still. Then I had a few commenters say the same thing so it’s not because I’m logged in either. Pretty confused on this.


  8. Hi everyone. I’d really like to upgrade to 2.7.1–I usually do so through an svn switch to the new tag. However, this time with the admin bar disappearing, I needed to rollback. What’s missing from this post is the location of the plugin replacement. I know there is such a plugin on viper007’s website, but is that THE plugin for WPMU? It only says WP, so I am uncertain. I’d like to find the replacement for viper’s admin bar before doing the upgrade. Or could you possibly put the plugin in the mu-plugins/ folder in the repository as an external (like akismet)?


  9. been running the plugin since it started and this is the first version that actually emptied my garbage. yeah. keep up the great work :)


  10. Is there anywhere I can get a list of the files that were changed as part of the 2.7.1 upgrade?

    My company was in the middle of a 2.7 upgrade when 2.7.1 came out and we have made some changes to the base code to accomidate a few changes requested by our user base. We would like to know which changes we will need to reapply after the 2.7.1 code refresh before we move forward.

Leave a Reply