I know it’s been a long while since I’ve posted and I know my last post promised frequent stories of my adventures during my European adventure. Did you think that I had been kidnapped and sold into sex slavery? I tried my best, but the slavers just didn’t seem to be interested in all of this *waves hand across torso and face several times*.
What really happened is that I couldn’t log into my blog. You see, I have the memory of a 95-year-old – and not one of those spry 95-year-olds with a wicked sense of humor who credit their sharp minds to a tumbler full of whiskey and a pack of cigarettes every day. No, I’m so forgetful that I have the passwords to various websites saved so that Google Chrome automatically populates them for me.
My phone doesn’t have Google Chrome.
I tried to log into my blog using several variations of the three passwords I tend to use, with no success. Finally, the security on my website decided that I was a Russian hacker and locked me out. I requested a link so I could set up a new password, and it cheerfully sent the instructions and link…to my blog e-mail. The problem was, I didn’t have my blog e-mail log in information and hadn’t bothered to get it for a couple of years, so I had no way to access it. When I got home and finally was able to log into my blog e-mail, I had something like 15,000 emails I had to purge! Hopefully there wasn’t a notification that I had won the Publisher’s Clearing House Sweepstakes or anything, because I didn’t even bother to sort through them first.
When I came back to the States, I had every intention of writing – but then my blog crashed. It probably had something to do with the fact that every time I had logged in for about a year, I kept getting warnings that there was a problem updating to the latest version of WordPress. Every so often, I would hit the button to try to do it manually and it would tell me that I had some sort of line error that was causing some sort of muckinfuch problem, and I didn’t know what in the hell it was talking about or how to fix it. So, I did what any normal person would do – I ignored it. Apparently the combination of my ineptitude and the lack of attention for so many months pissed my blog off so much that it finally decided I was no longer worthy of being a blog owner and it shut the whole thing down.
I seriously considered just letting my web hosting and domain name lapse. I mean, I had only written three posts in the past twelve months and only about 11 people read my blog anyway. But I hadn’t kept a copy of any of the 215 posts I’d written over the years. I know, I know – I have a serious problem with procrastination and motivation! But I wanted those stories – maybe someday my great-great-grandchildren would be interested in what a strange woman their ancestor was and what an odd and somewhat crazy life she led.
So, I called my web host and asked if they could fix the issue. They were willing to do so, if I was willing to pony up $80, plus a couple of hundred to renew my domain name and web hosting. I began to think that perhaps my great-great-grandchildren would just have to live in ignorance. In the end, as you can probably surmise since you are reading this, I paid the ransom and my website was restored, although now it now runs incredibly slowly and takes forever to load. I’m convinced it is a plot by Go Daddy to get me to subscribe to their “premium support” – especially since I now get weekly emails warning me that if I don’t do so, I could “lose website files, important emails and essential data.” I refuse to comply, so unless I start dating a computer savvy Russian hacker, it’s going to stay this way.
Grab a snack if you plan to read any other posts. It may take a while.
Now that the blog-drama is pretty much resolved (or as resolved as it’s going to be), I plan to get my money’s worth for the year and write more often (if I can overcome that pesky motivation and procrastination problem).
This time, I’ll save a copy to my documents – just in case.