Progress! In the unrelenting march to some ideal, feature rich, future we have to occasionally update the WordPress software which normally amounts to clicking on the Automatic Update link and waiting a moment for the updater to do its thing. Alas the 3.1 update did not do its thing and the blog was broken; left bereft with only the message:
Unable to even log in to see what the problem was I turned to my trusty FTP software to get into the blog. The usual suspects are the plugins which add myriad enhancements but will often cause as many problems. Renaming the plugins folder, so WordPress will not recognise it, allowed me to get to the login screen; and once in I was greated with the message
Clicking the link to run the updater again successfully updated WordPress. Moving all the plugins back into the newly created plugins folder showed that it was not the plugins at fault this time but the errors seemed to be from my own child theme. So we are now back with a hacked about a bit Twenty Ten theme which will break when the next update comes along. Ho hum.
Having added a Time Capsule to the mix of Macs it was somewhat frustrating to find my Snow Leopardified Mac was not working while ye olde iBooks running Leopard were purring away backing up flawlessly. I was stuck in the never ending “Making Backup Disk Available” bit. A seemingly common problem.
But today it started working and I am now backing up with the rest of them. So what changed? It would be nice to think that the return of Steve Jobs had something to do with it. Maybe installing iTunes 9 triggered something. But it was probably dropping the wireless network down to the b/g setting from the b/g/n option that made it happier. The slower setting is strangely the stronger faster setting for me.
While exploring Runtime Revolution I was unable to view the tutorial videos. I had the audio content but a blank green screen replaced the video content. It turns out the problem is solved by disabling the Perian plugin for Quicktime.
I also was unable to do the WordPress automatic update thingy. This one was solved by disabling the WordPress Automatic Upgrade plugin which was conflicting with the automatic updating process :-/
I just mention these in case you are looking for a solution to similar problems.