Oh snap!

Mistakes happen.  It’s inevitable sometimes, isn’t it…  the hardest part is trying not to let it get the best of me.  “It”  being my mistake of not backing up my db before doing an update.  I neglected to do it, and when I tried to do a point upgrade to Expression Engine, I somehow ended up with a clean install that overwrote my content.

It’s not all bad, though (at least I’m going to keep telling myself that until I believe it).  I’m going to take a lemon and turn it into lemonade.  I look at this as an opportunity to turn things around.  My only question being how quickly can I get it done?

Of course, this is not the best of times to kill one’s database.  There’s way too many other things going in my life at the moment that take higher priority, but I shall endeavor to do what I can (as always).  That’s sort of the testament to how I work:  I trudge forward, not fast, nor slow, but as unrelenting as I can.  Occasionally I’ll get a burst of speed that cranks me through pressure times (like this), and tough situations, but most of the time I’m just a one-step-at-a-time sort of guy.

If your curious, I still have all of my old flat-file content available.  My layout templates and Artcasts are very much safe from harm.  My only concern is that it might take me longer to go back to where I was yesterday than to move forward into tomorrow.

There’s also been times in the past that I’ve killed a DB on purpose, because of CMS experiments, or content changes, or whatever else I’ve done in the past.  This time, I really goofed up on something I wanted to keep.

So, to take the advice from a very wise and good friend “maybe this’ll give me the opportunity to embrace the new design without the constraints of old content”.