Masterpiece
*****
Excellent
**** 1/2
Very good
****
Good
**** 1/2
Just okay
***
Not for me
**
Definitely not for me
*

Lemonade for the #Bloggiesta?

bloggiesta

The Bloggiesta was a great idea for an event, and I’m really looking forward to the next one because I know it’ll be a lot less stressful.  Thanks, Natasha, for all your hard work! Thanks also to those who hosted mini-challenges as well.

Yes, I managed to stay up all night last night for the Bloggiesta! Unintentionally, of course. If you haven’t heard, here’s the post about how I lost 7 months of my blog. How’s that for an anchor post?! (I couldn’t resist some middle of the night humor.)

These lemons are a bit bitter, so I decided to make lemonade!  I’ve found out a few tips for you if you ever lose your blog:

  1. Go to your google feedreader and go as far back as you can for your own blog (hopefully you subscribe to it yourself).  I couldn’t believe it when I got to the end of mine and it was the DAY BEFORE the posts that got cut off.  I almost cried to have them all there.
  2. Then, start copying and pasting in your oldest posts, because if you start with the most recent, you’ll cut off the older ones because your feed can only hold so much memory.
  3. If you’re like me and have backdated reviews (a bad idea I’ve learned), go to google and enter in your blog name and the book title.  You may get lucky if the results show your link.  But don’t click on it, just click on the ‘cache’ underneath it.  It should come up with your post.  Yay — I got VERY lucky.  All five of the reviews I wanted were there!
  4. I decided that since I basically lost all my categories, I was going to put most of those in the tags instead.  Then, I’ll set up a redirection for the categories to point to the tags.  Tags are much easier to enter when I put in ‘s’ title, ‘r’ author, 5 stars, 2000s, and 0-199pp.  I just started reorganizing how I’m going to do that.  I’ll put setting and original language in the tags as well.  Then, when I get finished re-entering all my posts, I’ll have a really nice tag cloud for my blog.  I really like the 3-D tag clouds.
  5. I then went to my gmail trash and found all the comments for my blog that were still there.  It only went back to early May, but it’s something.  I’ll logout of my account and re-enter the comments as they were entered by the commenter.

So, all is not lost.  A lot of it is, but I’m grateful for what I can recover!  Also during the weekend, I did a few other Bloggiesta activities:

  1. Updated the Book Awards Challenge site sidebars to reflect the most recent winners and put links up to show where the lists were in wikipedia or other sites. (About 1.5 hours)
  2. Helped a friend find and tweak a new theme. (About 2 hours)
  3. Had an avocado and a couple of burritos with hot sauce during the weekend, but sadly, no beer or margaritas to go with them. (About .5 hours)
  4. Time spent finding out the reasons for the omissions and recovering a few posts (At least 12 hours)

Although I was heartbroken over losing part of my blog, I’m kind of looking forward to the changes I’m going to make to my site. And hopefully, my experience will help others not suffer the same catastrophe and/or know a little bit of what to do if it does occur.

7 Months Gone (TSS)

tearsSeven months of my blog are gone. [edited to add:  I've recovered nearly everything now except comments, but it took over 36 hours] Why?  For several reasons.  First, I tried to ‘upgrade’ to WordPress 2.8.  Didn’t I back up?  Yes!  I always back up before I upgrade.  But….  there is a little thing called a php.ini file that has limits.  Size limits and time limits.  I back up my blog at least once a month, but because I’ve been blogging for over 2.5 years, the size of my file is fairly large.  Therefore, every time I’ve backed up in the last few months, my backup was getting cut off at around mid-November 2008.  My host is Bluehost.com, who I have been very happy with ever since I went to my own domain.  But, they went to something called Simple Scripts instead of Fantastico, and it’s wiped me out.  Yes, I know there are more ways to backup than just an xml file.  I wasn’t worried, though.  I should have been.  I should have opened up the file and checked.  I didn’t even know how to do that until today.

What have I lost?  HOURS and HOURS of work.  Yes, I will be able to recover some of it from my feed reader.  I’ve not only lost posts, though, I’ve lot categories, tags, images, comments, custom fields, and my 2009 Books Read page and my 2009 Challenges page.  I’m heartsick at this loss, but I’m posting this now so that if you use WordPress, you can have a heads up on what NOT to do.

Here’s the minimum of what you need to do.  First, backup your blog by exporting it to an XML file.  Then open that file using Notepad and make sure that your latest posts are at the bottom of the file.  If they are, you’re okay.  If not, you need to find your php.ini file and set your limits higher to something like 32MB and 90 seconds maximum.  This is what the code will look like:

‘max_execution_time = 90     ; Maximum execution time of each script, in seconds’
‘memory_limit = 32M            ; Maximum amount of memory a script may consume’

Mine was only set to 30 seconds, hence the problem.  My xml file said ‘Fatal error:  Maximum execution time of 30 seconds exceeded in /home/insertyourfilenamehere/public_html/wp-includes/link-template.php’

If you already have 2.7 (or maybe it’s 2.8) or above, you probably don’t have to worry as you can do an auto upgrade from your panel.  So, I probably won’t have to worry about this again.  A lot of good that does me now!

Anyway, there are other ways to back up your installation before you upgrade.  I just wasn’t worried about it as my backup was always fine and it worked for me.  Until it didn’t.  Before upgrading, I would suggest that you follow the very detailed instructions that will let you know how to backup your blog properly in wordpress.

Sorry for the bitterness on a Sunday, but I hope this mishap will save someone else from the same grief!

Blog Widget by LinkWithin