Fireproofing WordPress 2.7
So WordPress 2.7 is out in the wild.
Nice one.
I have been using the pre-release on this blog and I really like it. It has some really nice features, and some plugins are now incorporated. Most important of these (to me) is the update feature, which means no more FTP.
For my sins, I host quite a few blogs on my servers. Confidentiality prevents me from naming them, but you know them and love them! The problem is that every time there is an upgrade, I have to flit from blog to blog, taking them off line, updating the files, updating the databases, testing them and then putting them back on line again.
Some may suggest that I use WPMU, the multiuser version of the software? I played around with that briefly, and may go down that path.
But, in the meantime I am going to have an easier life doing my upgrades.
I’m just a bit concerned that 2.7 may not be able to handle a red hot site like Head Rambles, with its profanities, blasphemies and general nastiness.
Is 2.7 well coated with asbestos?
A solid layer of asbestos with a Kevlar oversuit so no problems there. It was a last minute non-advertised patch (changeset# 12679.5) so 2.7 could be used with highly volatile sites such as the one you mentioned.
I originally made the suggestion on the “wp-testers” list with “Head Rambles” in mind.
Thanks Kirk M. I have made an appointment with the fire brigade to be here when I switch Head Rambles over though. Better safe than sorry?
It’s always good to be prepared for contingencies (you don’t have to feed them or anything?).