The MU forums will shortly be closing up shop.
WordPress 3.0 integrated everything that MU always did so it’s better to consolidate the forums too. There’s a MultiSite forum on WordPress.org and any queries about upgrading or problems using WordPress 3.0 should go there.
The old forums aren’t going anywhere but later today or perhaps tomorrow I’ll be making them read-only. You’ll still be able to browse the forum, and Google will still index the wealth of information already there but posting will be disabled.
So, thank you to everyone who contributed to the forum over the years. You helped make WordPress MU great.
I’ve just released WordPress Domain Mapping 0.5.2. This plugin allows you to map any domain on to your WordPress 3.0 or WordPress MU website.
New in this release:
- WordPress 3.0 support.
- Added “domains” page for superadmin to add domains to any blog. The user’s domains page can be disabled by the superadmin too.
- Added support for “www.” prefix in front of domains.
- Allow dashboard to redirect to mapped or original domain.
- Better support for SSL
- Translation file added for localization.
For security reasons remote login is now disabled if the dashboard is redirected to the mapped domain. There is a tiny chance of a man-in-the-middle attack during redirection, but it’s just as likely to happen when you’re logging in and sending your username/password to the login form. Call me paranoid.
I would like to thank Ron and Andrea who were a huge help developing and testing this release. Andrea has written a great post on creating a network in WordPress 3.0 plus instructions on upgrading from WordPress MU. Great stuff!
one dot one dot one dot one dot dot dot…. Yes, last week’s release of WordPress MU wasn’t to be the last one. This is. Really.
WordPress MU 18.104.22.168 fixes #1193 and #1195, two annoying but one liner bugs that crept into the last release.
This is also a security release fixing a bug in the installer that has existed for quite some time. If you can’t update yet, delete the file index-install.php immediately. That file is only used when you install WordPress MU for the first time so it’s not needed afterwards. Don’t ask, “I’m using version x.x.x, do I need to delete this file?” Just do it. Thanks Mad Sprat for reporting the problem.
The index-install.php in 22.214.171.124 is safe, but I’ve added a note at the end of the install recommending the file be removed. The file is not used after installation and it’s always a good idea to clean up unused scripts.
Get WordPress MU 126.96.36.199 on the download page or wait until your Dashboard upgrader finds the new release.
If you’re adventurous, download and replace the following files on your site to upgrade:
Sorry Jeffro! 🙂