It is kind of weird to write this, but as of today the bava is no longer powered by WordPress Multi-User. I have upgraded this site to WP 3.0 Beta 2. For almost three years now this site has been running on a multi-site WPMu setup that contained not only this blog, but jimgroom.net, wpmued.org (now a deprecated name space:( ), and several other personal sites. The bava WPMu install became my test bed for UMW Blogs over the last three years, and to see it return back to a straight WordPress site (though it’s not really that anymore with 3.0) is kinda bizarre.
I’ve been working with WPMu for more than four years, and I’ve literally written hundreds of posts on this blog about my work at hacking it. And I’ll be the first to admit I am the worst of hacks—don’t know a lick of code—but that being the case, WPMu made me. I can daydream that my b-movie posts or my tour-de-force toy blogging put me on the map, but it was my sophomoric work with WPMu and UMW Blogs that gave me a reason to blog just about everyday for almost four years. It was a good run, and I couldn’t have done it without Donncha—so thank you kindly. And while I know it’s time to move on, I certainly mourn a chapter of this blog that is effectively closing. I’ll still be blogging through the transition of UMW Blogs from WPMu 2.9.2 to WP 3.0, and there is much to talk about and figure out there yet, but with this post a piece of the bava is dying. But, that said, I wouldn’t trade it for the world because, as William Faulkner says, “Given a choice between grief and nothing, I’d choose grief.” Good bye Mu, I’ll miss you!
On a more prosaic note, the upgrade from WPMu 2.9.2 to WP 3.0 Beta 2 went extremely smoothly following this tutorial (just be careful of the wording in Step 1, what he means to say is replace all files and folders except wp-content, leave that be). Some initial observations:
- Userthemes is further borked after the upgrade (no surprise there), but it looks like WP 3.0 Beta 2 has theme editing built-in across sites. I may be wrong, but when I deleted the Userthemes plugin, an edit button showed up on various blogs. This could be awesome, but it also means I have to find a way to un-usertheme a lot of blogs that were using Userthemes in UMW Blogs. This will take some looking into.
- The various mapped WPMu sites I had on by own WPMu install worked without issue. jimgroom.net is a full blown WPMu site within a site (or the correct terminology now would be network within a network?–not sure.) Those worked fine, as did some straightforward mapped domains, which is nice. But, I am still using the mu-plugins folder with various plugins that control these functions. Need to experiment with how much they bork when I start deleting MU plugins, we’ll see.¹
- Need to test the Sitewide Tag Pages Plugin that Donncha created, this plugin has been key to the syndication framework on UMW Blogs, but I’m not sure it will be managed for too much longer even if it does still work. Need to find out if some global posts/tags/terms are being used across sites. We’ll see.
- On that note, need to see what FeedWordPress is all about in 3.0, that will prove crucial as well.
- Need to figure out the whole Child Theme thing, as well as test out a whole series of plugins while cleaning out my mu-plugins folder.
As you can see my list of things is long, and there is much work ahead and I plan on blogging it all. But as of now a big step 1 is done [sniff].
¹ Turns out mu-plugins will be supported for the foreseeable future reframing the mu-plugins from the association of MultiUser to “Must-Use,” basically making them active across entire installation (which means more than one network). Also, there is another cool feature for keeping WPMu sites like UMW Blogs afloat: “Drop-Ins.” To quote this excellent article on both of these new additions to WP 3.0:
Some core functionality of the WordPress core can be replaced by so called Drop-Ins. Those are PHP files on specific locations that get included if they exist. The inclusion is done for a specific task, for example
db.phpget’s loaded to replace the default PHP database class. So you can replace it with one that is faster, more stable and secure for example. Drop-Ins exist since various versions, depending on them. The Multi-Site since 3.0 naturally.
This means it should square any sharedb.php issues with UMW Blogs, which is mint. It is also why sunrise.php for the Domain Mapping plugging kept working seamlessly. See the article above for a list of WordPress Drop-Ins.
Additionally, as my turn to terminology in comments might have suggested, I went searching for posts about the new terminology being used in WP 3.0 as the merge of WP and WPMu comes to pass. Here is another good post on the new terminology in WordPress 3.0 for blogs, sites, networks, etc., and here is a nice presentation on it as well. The changing terminology is something I am actually really interested in, and may be the basis of a longer series of thoughts about the importance of terminoloy in watching WordPress develop and grow.