Select Page

Following on from my previous post I “successfully” upgraded 3 of our WordPress blogs (well I say successfully compared to my experience with upgrading MacBites)

I don’t think that Siteground’s control panel likes to play nicely with Safari. On a number of occasions, I have received an error:

“Operation could not be completed. (kCFErrorDomainCFNetwork error 302.)”
(kCFErrorDomainCFNetwork:302) Please choose Report Bugs to Apple from the Safari menu, note the error number, and describe what you did before you saw this message.

This error has usually happened whilst installing, upgrading or removing an application (Siteground, like many webhosts, use the Fantastico one-click install application to allow customers to easily install applications on their websites). This error often causes the installation/upgrade to fail.

After upgrading 3 sites to WordPress 2.6 (this was the only option available via Fantastico – to install a different version would have required a manual install), I was confident that I could complete the installation on MacBites.

Oh, how wrong was I as the famous kCFErrorDomainCFNetwork error 302 error reared its ugly head. When I opened the MacBites home page, the look of the pages was fine (I did not expect any problems because the upgrade should leave the WordPress theme alone) but there was no content.

When I logged into the admin section, a message popped up to advise that a database upgrade was needed. I duly clicked the button – and my content promptly disappeared (luckily I had taken a backup of the ENTIRE site before starting this whole fiasco).

To cut a long story short (just like the night which was also long)…

I uninstalled WordPress (via Fantastico) and re-installed WordPress 2.6 (via Fantastico) – I did this using Firefox.

Using FTP, I uploaded the theme to the wp-content/themes folder, uploaded the photos to the wp-content/uploads folder and uploaded the plug-ins to the wp-content/plugins folder – in other words, I restored the wp-content folder back to it’s previous state.

I then replaced the MySQL database with my backed-up local copy and fixed the Categories issue – as per my previous post.

The final problem was the Twitter Tools plug-in which displays the latest Twitter post from MacBites – it was displaying a blank space where the content should appear.

This plug-in actually copies the the Twitter posts to a database stored within your site (rather than live-linking to Twitter). When I opened the database there were over 300 blank records which I deleted.

So was it worth it? Well it does mean that when the aforementioned WordPress app for the iPhone is released, we’ll be able to blog live from the iPhone.