I just released WordPress MU 1.3.3 and it’s now available for download. This is a critical security release based on WordPress 2.3.3 and everyone is encouraged to upgrade.
Here is the forum announcement. I also listed the 3 security fixes that were the reason for 1.3.2. If you haven’t upgraded yet, please do.
29 thoughts on “WordPress MU 1.3.3”
good to see WordPress MU is following quickly the releases of WordPress.
There’s a question in my mind, maybe you can answer it:
Is it possible to have WordPressMU installed that it works with not only sub-domains but fully separate domain names?
WPMU rocks! And another update. They are going crazy with the updates! WP 2.3.3, Prologue updates and now WPMU again. Worpdress is rolling hard this year!
Greg – there are a few hacks out there for getting multiple domains working off one WordPress MU install but they don’t work very well.
I’m sorry to read that, because its hard to update a lot of singe wordpresses, and i hoped that WordPressMU would be a better solution for that, with the addition of working separate domains.
I’m not a big programmer, but wouldn’t be that an development worth?
I would like to help in any ways if there would be a movement in that development. donating hostnames for testing, etc..
I’m in hearty agreement with Greg. I also have a number of WP installs (on different domains) to update. Managing all through MU would be fantastic.
Thank you for your hard work, Donncha
Donncha, if I may ask a quick question:
If WordPress.com (which uses MU) supports domain mapping–then why can’t the downloadable version also support mapping?
Sorry–this is probably an ignorant question from a non-techie. 🙂
David – the early init code in WordPress MU and the version that runs on WordPress.com is very different. There are quite a few custom bits of code in there that, like all long-running sites, accumulate to reflect business and policy decisions.
The best place to put domain mapping code would be in wp-content/sunrise.php, well before the current blog and site are discovered by wpmu-settings.php. Anyone up to the challenge?
That sounds way above my head, Donncha 😀
Why not make that a public challenge 😉
Thanks Donncha 🙂
It is definetly possible to run WordPress MU with several domains!!
I use one WordPress MU installation that handles about 10 of my domains. This is achieved with help of the plugin Multi-Site-Manager (http://wpmudev.org/project/Multi-Site-Manager).
It is actually quite simple: download the plugin and drop it into the MU-plugin folder. For the sake of it, think about myMUdomain1.com as your main domain, where the MU database is situated. You want myMUdomain2.com also running on the same installation.
Go to PLESK (or whatever you are using) and add myMUdomain2.com as domain alias (no need to fiddle with the text-files). Make sure you have something called DNS-syncronization activated. You should now be able to create a new blog myMUdomain2.com from within the sites tab of your original MU-installation.
One drawback for me is that I can not use subdomains on these domains. This might be fixes by adding a Server Alias *.mydomain2.com at the appropriate place in the vhost.conf (which didn’t work out for me) or somewhere else. I don’t want to use subdomains anyway, so I don’t really care. But if you find out how to do it, please let me know!
Martin, thank you so very much for sharing that! It is a great help! I will give it a shot. Donncha, what do you think of this solution?
May I ask: how have you found the theme/plugin compatibility on MU compared to normal WP?
Martin, I see they say there that “For these settings to be effective, each address designated as a site (domain + path) must be pointed by your web server at your WPMU installation.” This is probably a n00b question, but what if I want to have a WP installation at mysite.com/subfolder. What does one do then?
If I may make this a little more practical: all my sites are hosted on BlueHost. Will I need to make any changes?
Excuse me for being pedantic, but I don’t think that you (as lead MU dev) should have so many brutal ads on this blog – especially ones that create ad links out of words like “security” in the context of “critical security release”. It’s like you’re making money out of the security fix.
Stuart – the adverts are chosen by Google, not by me and only appear on older posts such as this one, and now that you’ve commented, you won’t see them any more! 🙂
I had problems upgrading from wpmu-1.2.5a to wpmu-1.3.3.
We’re migrating to a new server cluster, so I’ve done the upgrade over there, after migrating the DB.
At the end of that thread, I added some suggestions for future version of WPMU to make using secondary servers/clusters easier, while maintaining the same functionality.