And…we’re back!

Apr 20, 2012 by

If you’ve been following my Tweet stream, you may know that I recently had some website issues. Apparently, my website theme got ‘corrupted’ somehow, which meant I couldn’t log in to change, edit or post anything for almost a week. After much searching, trying to read through incomprehensible ‘help’ pages and asking friends and strangers for help, I finally broke down and called Bluehost, my website hosting company, for help. And they were great! They figured out the issue and fixed it for me so I could get on with my website life.

Though it was a huge pain in my ass to deal with all of this, I decided to view it as an opportunity to change the theme and look of my website. Soon, I’ll have a new header/banner too and a new name for the site will be revealed. In the meantime, I thought I’d share a few lessons I learned when my website crashed and burned:

  1. Good work is never doneThis is a lesson I’ve already learned a few times, but that doesn’t mean it isn’t still valuable. A couple of years ago, I made the decision to create this website through WordPress and pay for hosting it at Bluehost rather than using an easier, free but less flexible blogging tool. It took lots of work to get it set up and that work just keeps right on.
  2. When they tell you to update it, update it – I had gotten a few notifications that my theme needed to be updated, but I didn’t pay attention. When I had updated it in the past, it had usually broken one or more of my plugins and I didn’t feel like dealing with it. Well instead, I had to deal with an even bigger problem. Next time, I will update it.
  3. Stop whining and ask for help – I tried and tried to figure out how to fix it on my own. I searched and searched through WordPress’ less-than-helpful ‘help’ pages (that’s another lesson: WordPress isn’t always that helpful) with the hopes of figuring out what was going on. I struggled to try and implement some of the solutions they provided – all to no avail. After nearly a week, I finally gave in and called Bluehost. 10 minutes later, it was fixed! I could have saved myself so much time and frustration if I had just done that in the first place. Lesson learned.

Thanks for sticking with me through a lot of site maintenance. More posts will be forthcoming soon!

Flickr photo courtesy of user viviandnguyen_

Related Posts

Share This