WordPress MU 1.2.5

A new release of WordPress MU, the multi-user, multi-blog version of WordPress is now available.

This is a security release to address issues brought to our attention by Alexander Concha who I must thank for his unfailing patience while we sorted out this release.

Edit: this release is based on WordPress 2.2.3. Unfortunately a last minute bug crept in where post titles looked like post slugs when viewed on your blog. I quickly rolled together a new minor release, 1.2.5a which has an updated wpmu-functions.php. The download page has been updated too. If you have already updated your install, all you have to do is go to this page and download a new wpmu-functions.php and place it in your wp-includes directory. Apologies for the mix up!

Edit 2: I forgot to mention yesterday that a lot of the functions that were in the files in mu-plugins/ have been moved into wp-includes/wpmu-functions.php so move those files out of the way if you get errors about functions already existing. As stated previously on the forum, kses.php is synced with the one in WordPress which means class and id will be stripped from posts. If you’re happy for your users to use the class and id tag attributes then the following function will come in handy. Put it in mu-plugins/kses.php where it will be activated automatically.

function addabitofclass( $tags ) {
    global $allowedposttags;
    foreach( $allowedposttags as $tag => $attr ) {
        $attr[ 'class' ] = array();
        $attr[ 'id' ] = array();
        $allowedposttags[ $tag ] = $attr;
    return $allowedposttags;
add_filter( 'edit_allowedposttags', 'addabitofclass' );

The observant among you will notice I forgot to assign the result of the filter in wp-includes/kses.php. This has since been fixed but it was too late for this release. Making it a global in the function above was a suitable work around.

23 thoughts on “WordPress MU 1.2.5

  1. Hi,

    One of my blogs is on a WP MU 1.2.4 installation on a PHP 5/MySQL 5 coupled webserver and there is a serious problem with special characters – in my case – it is the Turkish characters which are showing as question marks.

    The encoding is left at default which is UTF-8.

    At the same web server configuration, I have 3 WP installations both English and Turkish versions none of which bring about the same character problem – Turkish (and characters) are just fine.

    I don’t know yet where to report this assuming it’s a bug.

  2. Hey donncha, i have 1.2.4 then if i replace wpmu-functions.php and i remove of the way “mu-plugins/” files, it will work? gon be okay my blog? doing those change will make my 1.2.4 fixed up, or do i have to upgrade to 1.2.5, please if you can tell us, thanks very much. Regards.

  3. Waldy – you should upgrade. There aren’t that many changed files but there are security holes in WordPress itself. That’s why you should upgrade to 1.2.5a, not just wpmu-functions.php

  4. Thaaaanks. After i went lately to sleep 🙁 translating the 1.2.4 to spanish 🙁 no i have to translate it again into spanish for version 1.2.5 but does’nt matter because im happy :D. Have nice days Donncha i will follow your blog. Im .Net programmer (c# vb j# ).

  5. Donncha thanks again, my wordpress mu, some bugs fixed:

    Bad request header in IE (no more 404) good !!!

    Seems faster !!!

    and sure with that fix up you released 😀


    We Trust WordPress 😀

  6. Ok, looks like I’m using 1.3.2 version of WP MU. I’m running a controlled MU with just a few trusted users. I really need to allow class attributes, so I created a kses.php file with the lines above in it, and uploaded it to mu-plugins/kses.php as instructed. However, that causes those lines to be written at the top of the admin (as though they were an error). Is that because I’m running 1.3.2 instead of 1.2.5? I’ve gone through all of the forum posts regarding kses, and have seen many people get a little rude, implying that reading such posts will provide the answers, but frankly, it’s just not the case (at least not for me). I’ve tried the various “solutions” to no avail. Has anyone come up with a simple answer to this? Like a plugin?

  7. Donna – sounds like you need to put a <?php before that code and ?> after.

    Hopefully those characters come out, but if you’re subscribed to this thread and they don’t appear in the email check this page because I’ll fix it if necessary after I submit ..

Leave a Reply

%d bloggers like this:

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.