Not. My. Fault.

Seriously. My website was working just fine one day, then a week later when I went to post to my blog — and without me doing anything to it — the whole site was kaflooie (that’s a technical term).

First let me say THANK YOU… for nothing, GoDaddy techs. All those backups you made? What’s the point, when clicking on Recover doesn’t do anything?

Secondly, THANK YOU, Diarmad, for fixing whatever it was that GoDaddy techs couldn’t/wouldn’t.

And finally, THANK YOU THANK YOU Wayback Machine for archiving websites! Every so often I remember to save a “snapshot” of my website there. The ones in May were corrupted but one from mid-April is fine. While I don’t know how to just plug that into my fixed site (if that’s even possible), at least I haven’t lost all my content. <phew>!!!! [Note: I donate to Internet Archive because it’s an incredibly valuable service!]

So yesterday I worked on getting the website up and running from scratch. The first iterations were ugly with almost no content. As the day went on it started to shape up, but as I plugged away at it I became infuriated, knowing that all this work was due to nothing I did, and yet the culprits wouldn’t fix it. Diarmad said that the coding deep in the bowls of the site, stuff that I absolutely do not touch, had been corrupted. He blames it on the fact that… no, I’m not going there. I don’t really understand it. I used to do website coding but that was just HTML and websites have gone way beyond that now.

Part of my frustration was that I felt that I should have gotten better tech support. Neither of the techs were native speakers of English, which doesn’t matter in everyday life but does when there’s technical talk involved (and that talk was all via text). For example, what was I supposed to make of sentences like this one: “…the core files are the contents related issue which beyond scope of supper, this needs to be either reviewed by your end by the well-versed developer. Or else you can opt for the expert services which we provide.”

It was right after that when I decided no way was I going to pay for GoDaddy’s expert services to fix the issue that they caused.

Yesterday was a seven hour day, by the way. Because I was so bored and had nothing else to do, right? But that was yesterday and that’s done and over with.

Now that I’ve got the framework set up almost right, I can start plugging in the content I’ve retrieved from Wayback Machine. It’s saved in my computer as well. Can’t have too much redundancy, obviously.

However, no more seven hour days. I’m going to pick away at the rebuilding process because in fact (or should I say incredibly) I like rebuilding the website. I like seeing the content suddenly appear and I like making it look pretty. When I used to do websites for clients, plugging in the content was always what I liked doing the most. It’s the artsy part of it that attracts me. That’s why I don’t need to ruin that pleasure by making it all-day slogs every day. That’s why the website isn’t very useful right now.

And so this is the long way of my apologizing again for the state of my website. It’ll all eventually be okay, just not today.

Oops, I see something else I need to fix right away. Bye for now!

Bookmark the permalink.

About lifstrand

Lif Strand began writing fiction when she was a kid. Nobody read her stories. A former Arabian horse breeder and endurance racer, then reporter and freelance white paper writer, Lif lives in a straw bale house off-the-grid and writes fiction once more--or at least whenever she’s not scooping horse poop, taking photos, or playing with fabric art.

Comments are closed.