Comments on: How to restore your hacked WordPress database from Google Cache through Ruby

By: cati kaplama

cati kaplama — Fri, 23 Jul 2010 19:24:51 +0000

good work

By: Jacob Seiner

Jacob Seiner — Sat, 27 Mar 2010 04:45:11 +0000

You could use Warrick. It does a darn good job of recovering lost sites. http://warrick.cs.odu.edu/

By: What Would You Do If Somehow You Lost All Your Blog Content? | Tips and Tricks

Wed, 24 Mar 2010 07:16:43 +0000

[...] How to restore your WordPress database from Google Cache through Ruby [...]

By: Patch67

Patch67 — Wed, 02 Dec 2009 19:38:24 +0000

Pretty cool. Same thing happended to me a couple of weeks ago but I manually rebuilt my post from Cached pages (I didn't have that many so it was ok). If you don't mind, though, I will refer to this method in my Squidoo lens about my whole ordeal. Thanks again.

By: promosyon

promosyon — Sat, 31 Oct 2009 09:14:51 +0000

Thank you..

Promosyon

By: kino tachira

kino tachira — Mon, 12 Oct 2009 12:52:05 +0000

mirandoquecar??cterdeltrabajo

By: john

john — Fri, 09 Oct 2009 20:56:49 +0000

i get access denied when using grep this is the first time i have used grep…this is what iam doing mysite.com C:/filelist1.html > C:\filelist2.html
than pressing enter and i get access is denied?

Any suggestions on whats happening here?

By: Restoring a Wordpress blog from Google Cache

Restoring a Wordpress blog from Google Cache — Mon, 09 Feb 2009 02:42:29 +0000

[...] How to restore your hacked WordPress database from Google Cache through Ruby coding, hustle Subscribe to RSS feed a2a_linkname=document.title;a2a_linkurl=location.href; Leave a Reply [...]

By: Max

Max — Mon, 26 Jan 2009 22:35:04 +0000

I've got exactly the same problem and this blog post has been a great help. Some additional tips if anyone stumbled across this…

1. getting your stuff from Google's cache is a good thing — you never know when it's going to disappear and it helps you mangle things on your own computer.
2. it hammers home the necessity of good, semantic CSS/HTML for your blog theme
3. you could get ruby to add a random wait before getting the next page. Google doesn't like people slurping 150 cached pages in 3 microseconds.
4. wget has an even better flag for waiting… –wait=X (see:http://linuxreviews.org/quicktips/wget/)
5. Should of had Cron doing my bidding on the database backup! (more: http://help.joyent.com/index.php?pg=kb.page&i...

By: houshuang

houshuang — Mon, 12 Jan 2009 12:16:32 +0000

Steven, it probably took me something like three hours. But as I said, that program could have been written in 20 minutes by someone who used Ruby on a daily basis (it's not even difficult Ruby, I had to look up the syntax for even simple stuff). And yes, I thought I had a backup floating around on my hd, but couldn't find it. I relied far too much on my host – quite ridiculous really, I know.