WordPress MU, the multi blog version of WordPress that runs on WordPress.com has been updated.
Version 2.6.2 is now available for download and is a required update. WordPress MU isn’t vulnerable to the security bugs that were the reason for WordPress 2.6.2 but it does contain a number of important bug fixes, including:
- xmlrpc.php works better if you use multiple sites. #735
- get_option() wasn’t reading all options.
- Configurable media buttons on the Write page. #598, #738
- 404 “file not found” errors on folder installs is mostly fixed. #745
- And more .. (timeline)
PS. Don’t forget the voting is now open in the WordPress MU plugin competition.
PPS. Registration is now open for BarCamp Cork II on November 1st. I’ve put my name down to give a talk there.
25 thoughts on “WordPress MU 2.6.2”
Much appreciated Donncha!
Hi, Thank you… It will be more better if are in spanish… Thnk
Sweet! Thanks Donncha!
The link doesn’t work…
Richard – they worked for me!
I must be tripping, but this is what I see: http://bui4ever.com/files/2008/09/picture-1.png. Let me clear my cookies and try again…it might be cached.
I’ve upgraded and I have to say I don’t remember seeing the little number on the Plugins tab telling me how many needed to be upgraded… but I like it
Just like to add my thanks for spending so much time doing all the work on WPMU
coole realy it very cool thats given wp in multi languages thanks for the link
Richard – thanks, fixed that link. I thought you meant the download links on the download page!
Donncha – You know me, just being lazy and trying to download directly from your link! Thanks! 🙂
Can you give us any more details on that get_options() problem? We’ve had a client WPMU site with some odd problems, and I wonder if it could be related.
Dougal – Unfortunately get_option() would only return values for autoload=’yes’ records. Here’s the changeset: http://trac.mu.wordpress.org/changeset/1490
There’s no ticket as Will Norris emailed me directly about it. Think that may have caused your problems?
I’ll have to re-check, but I think in our case, the options were set to autoload. We’ve been suspecting a problem with their memcached object cache (either the plugin under MU, or the daemon itself, which is not the most current version).
Thanks for the info!
But I don’t understand why WordPress Mu does not inform users that there is a upgrade :S..