Upgrading to 2.8 [UPDATE: make that 2.9]
UPDATE: 090617 – So at roughly 10PM, the site is back on it’s production box. When you see this message depends mostly on how quickly your ISP refreshes it’s DNS records.
For some time in the after noon, you might have noticed some fishy things around the site, funky PHP errors about missing include files and what not. Generally, the errors were mostly with the admin pages, but sometimes did affect the header. None of the content was affected, fortunately, but it did wreck havok with me trying to manage unruly plugins that decided to break with the upgrade. Admin-ssl did a bit of damage, but others contributed to the error-generating frenzy as well. I had to uninstall some of these plugins, so you might notice a bit of reduced functionality (non-automatic https logins, chiefly) until they are updated.
In the end, the production server and the backup server were upgraded to WordPress 2.9, a non-stable build. Generally speaking, I’m super happy with it’s features, namely not having to manually scp over new plugins, and it’s new UI for widget management. I’m not sure if the plugin management upgrade is a 2.9 thing or a 2.8 thing, but the widget UI is listed as a 2.8 feature for sure, and it’s much prettier. =P
Original Post follows:
OK, so WordPress doesn’t like my particular configuration, lol. I’m gonna listen to my own advice and do it on a fail-over server first. =P
