Not filed under “sick children”, but it could have been

My blog was sick. Just vaguely sick, the sort of thing you could ignore mostly and just let niggle, like a cough that wasn’t going away. But it was getting worse. I thought maybe updating to the new version of WordPress (as all good bloggers should do when they’re told to) might help. I even took the heretofore unprecedented step of backing up first.

Then it turned out I couldn’t download the backing up widget. I got another one instead, and that worked okay. I clicked the “Automatic upgrade” button, and nothing happened. I kept trying for about a day, just in case the internet stars were misaligned, but they didn’t realign on their own.

I even contacted my hosting company and asked for help. The nice man couldn’t replicate my problem and suggested I clear my cache. That seemed to help, and I felt silly. Then it turned out it hadn’t helped at all.

I decided there was nothing for it but to do the update manually. I started copying over files. It appeared I could only do them one at a time. I soldiered on. When I came to folders within folders, I had to make the new folders and populate them, one file at a time. I suspected this was not what I was meant to do. As I clicked on the folders and saw what was in them, I realised it would probably take me a week. Without sleeping.

I finally asked for help. On a more local level. It’s such a cliche, but my husband does know more about this stuff than I do, even though he doesn’t have a blog. He knows what FTP means and how to make it happen. Thank heavens for husbands, and similarly enlightened people. Transferring the whole thing at once, in three batches, was but the work of a few minutes and not nearly as hard as the instructions made it sound.

Hooray! said I. A whole new day of functional blog was dawning with the advent of WordPress 4.1. But no. The glitch was still there, and getting worse. Now my Jetpack (which minds my stats and various other widgets) was no longer connecting. WordPress.com no longer recognized me. My blog was still there, still working, but I felt as if some insidious termite was breaking it down pixel by pixel.                                 .

Finally, last night, I tried my hosting company’s chat help again, and this time they agreed that there was something wrong. When the tech guy you’re chatting to replies “Hmmm,” you know you’ve presented them with something interesting. In the end I had to pay real money for an unique IP address that I need because something happened to their server. (I shouldn’t need it for long, and then I’ll get most of the money back, but it’s hardly ideal.)

And this morning I logged on and there was my blog – instantly, not after ten seconds of a page not found message – and my stats were back and WordPress.com knew me and I had to fix up all the things that had gone astray and everything was shiny and working the way it should.

And it turned out that I really do care a lot more than I thought I did about this blog and I’m glad the backup widget worked because if I hadn’t done that I’d definitely have been freaking out because as it was I was surprisingly tetchy and stressed about the whole thing. So the moral of this story is to back up your blog, boys and girls. And that if something seems wrong, you should get to the bottom of it before it gets worse. Which is probably a perfectly good metaphor for life, too.

One thought on “Not filed under “sick children”, but it could have been

  1. Pingback: Irish Parenting Bloggers | Not filed under “sick children”, but it could have been

Leave a Reply

Your email address will not be published. Required fields are marked *