I’m not exactly sure what happened, but here’s the brief rundown… the other day I see the “urgent security release” news about WP v2.3.3 and send off a line to my buddy who runs the server that BT is hosted on about it. He does an update after executing some backups, says he followed the instructions to the letter, and – poof. BT completely vanished from the face of the interweb. Uhhhh, ok? Now I trust he did the install fine, but unfortunately while I did disable any plugins I had running just to be on the safe side, I did NOT disable K2 as my theme. Considering I was running something around RC1, I’m not sure if that was the issue or if something else was the root of the problem. Suffice to say K2 started puking due to suddenly being unable to find a function in a WP include file.
So next step, do what I can do get K2 back up and running. I decided that rather than try and repair the current installation I’ll just back up the current one and install RC4. Which worked to an extent, but yet there was still some “set in WordPress but somehow affects K2″ settings that were still throwing some behind-the-scenes errors when trying to reference a small handful of files. All told from the “oops” point, it was probably 20 minutes of back and forth with me trying to fix things in the admin side and my buddy reporting on what PHP errors were still being thrown by the site. Good times.
Next time we do an update, K2 is being safely put on the shelf and reinstated once things appear to be all patched up. I still have some minor tweaks to make to the new install of K2, you may notice that things are a slight bit different on the site than they were before (a little less black, no HTML sidebar in the rightnav…) but I’m going to have to find the time to make these little adjustments. Soon.