Five Hours of Work, For This?
Thanks to some kind of snafu, I've spent the last five hours trying to restore my blog's template.
The story goes like this: I went in to add some new taglines, and I discovered that at least half of the HTML, along with about 300 of my taglines, had vanished for no reason. Since I had no clue how to fix it, I had to go in and reset the whole thing. I think I got everything fixed, but I'm still short about 75 taglines. I'm at an even 1000 right now, but I think the number will be back to its previous glory in no time.
I have no clue what caused it, but I just hope this problem doesn't occur again. If it does, there's going to be hell to pay for sure.
The story goes like this: I went in to add some new taglines, and I discovered that at least half of the HTML, along with about 300 of my taglines, had vanished for no reason. Since I had no clue how to fix it, I had to go in and reset the whole thing. I think I got everything fixed, but I'm still short about 75 taglines. I'm at an even 1000 right now, but I think the number will be back to its previous glory in no time.
I have no clue what caused it, but I just hope this problem doesn't occur again. If it does, there's going to be hell to pay for sure.
posted by Matt Sutton at
4:54 PM
4 Comments:
I'm just happy you got it back! I was worried when I first saw it.
I was asked to pass this along from Rob.
"It's a Blogger issue. When Blogger is reading to a template to publish (or republish) pages, if the template is long, the connection can time out as it's publishing pages, causing whatever of the template it didn't read to vanish. I know this because it happened on Butch's blog, too. If your template has all 20,000 zillion of those taglines in the template's actual code as I suspect it does, this is probably something that is going to happen to you again.
I'd suggest one of two things: 1)keeping a txt file backup of your template. I, thankfully, keep regular server backups so I was able to just yank a copy of the template off the server and fix Butch's blog within seconds.
2)reducing the size of the template. In this case, that would probably mean either removing the quotes script entirely or making a database file with all the quotes in it and putting a much smaller script in the template code that refers to where-ever the database is hosted.
Hope that helps."
Considering I'm up to about 1200 tags now, I think I'll probably back up the template every so often as a txt file. I'm not tech-savvy at all, so I don't know how I'd work that whole database thing. But if the txt backup works, I won't complain.
Man, the firewalls at work. *kicks them* ANYWAY.
Databases are not nearly as scary as they sound. The bigger problem isn't the database, those are fairly easy to create.
The problem (for you) would be creating the script code. Since it would require a custom script, and I kinda doubt you're fluent in MySQL enough to do such a thing. You might find a similiar script on a site floating out there and just tinker with it, but again, it requires a working knowledge of MySQL, JS, or (likely) both, for a 1200 + entry database.
So yeah, long story short, keeping a backup would probably be the easiest way for you.
Post a Comment
Subscribe to Post Comments [Atom]
<< Home