We may need another minor MU release due to some outstanding bugs.
12082 is harder than it seems to fix because older versions stored the attachment path differently. Editing images doesn’t work in MU right now. I need to install an older MU and examine how files are stored there.
There’s the wp_die() problem and this WP_DEBUG ticket, 12041, comes up when installing MU. That’s easy to fix. It’s a major problem because new users are seeing a PHP error when they haven’t configured their database correctly before installing.
And a small curl fix somehow escaped my attention when merging.
I’ve also given some thought to upgrading current MU sites – we’ll need a version of WordPress 3.0 that’s packaged like an MU zip file. The only real difference is the directory will be “wordpress-mu” instead of “wordpress” and it’ll be hosted on mu.wordpress.org like current downloads are.
nacin, 
wpmuguru, and 4 others are discussing. 
Andrea_r 7:27 pm on February 2, 2010 Permalink |
And oddly enough if a user’s db password is 6 characters or less, it also dies.
Donncha 1:06 pm on February 9, 2010 Permalink |
I couldn’t replicate that. I tried installing with a 5 character password and it worked fine. Maybe a permissions problem?
arena 9:32 pm on February 2, 2010 Permalink |
Is there any bug when plugins defining taxonomies (register_taxonomy) while loading ?
wpmuguru 6:48 pm on February 3, 2010 Permalink |
Contact your plugin author.
Luke 5:48 am on February 3, 2010 Permalink |
Just a little food for thought, but I took MU 2.9.1.1 and installed it today.
I created a couple blogs, activated a different theme for each one, and a plugin or two as well.
I then dropped all files except .htaccess and wp-config.php, and the wp-content directory.
I then took the WP core trunk, and plopped it right down in place, just like one would with a manual MU upgrade. (I did replace the themes in wp-content, as a note.)
Not a hiccup one. Went smooth as silk, as per Ron’s post here the other day, and nothing different than I’ve done hundreds of times when manually upgrading MU.
I then added a couple more blogs, and that went “like it normally would”.
Not that there probably aren’t a few minor issues laying around, but the work thus far has been very good.
Ryan 6:02 am on February 3, 2010 Permalink |
12082 is probably the same as 12044 which is fixed in WP trunk.
Donncha 5:27 pm on February 5, 2010 Permalink |
Thanks, applied those to my test server and an upload worked just fine. Checked it into the MU 2.9 branch.
wpmuguru 7:03 pm on February 3, 2010 Permalink |
Keep the built in upgrade server api in mind as well because until upgraded to 3.0, MU will use the MU upgrade server.
nacin 11:37 pm on February 3, 2010 Permalink |
I went through the core WP 2.9.1 patches and came up with these that also appear absent in MU 2.9.1.1:
http://core.trac.wordpress.org/changeset/12476 – $rss->__destruct if !is_wp_error()
http://core.trac.wordpress.org/ticket/11537 – switch to encodeUnsafe when falling back to Services_JSON
http://core.trac.wordpress.org/changeset/12466 – $wpdb typos in maint/repair.php
http://core.trac.wordpress.org/ticket/11502 – square buttons
Donncha 5:38 pm on February 5, 2010 Permalink |
Thanks Nacin. Merged those changes.