The Real Blogger Status

One of the most useful skills, when maintaining and publishing a blog, is backing up the content. As you publish a blog, it's a very good idea to periodically backup the content - comments, pages, and posts. Sometimes, backed up content may save you hours of anguish.

There are three possible dashboard wizards, used to recover a blog with a corrupt template aka "500 Internal Server Error". The Template Designer page. The Template page. The Template Editor ("Edit HTML") page. With most blogs, one of the three can eventually be used, to install a clean, new template - and recover a blog that's offline because of the broken template. Some blogs, unfortunately, cannot be recovered this way.

Of the many Blogger Mysteries that confound blog owners and readers, none are more obscure than the many bX codes. Some problems, reported in Blogger Help Forum: Get Help with an Issue , start so innocently. As I edited the Template HTML, I saved my changes - and the bX error suddenly appeared. Each different bX code refers to a different problem, with Blogger in general. Of the bX codes that refer to template corruption , each different bX code may refer to a different template corruption problem.

We're seeing a few reports, this week, in Blogger Help Forum: Get Help with an Issue , about blogs with broken templates. I tried to log on to my blog, and it shows up an error message. I've done it several times on different browsers, but no change: the error code is bX-uukqqu. It appears that the "bX-uukqqu" is from the owner attempting dashboard access. Trying to view the same blog, I see the ubiquitous "bX-v2vqfh". Both codes reference blogs which show up, in an HTTP trace, with the monolithic message "500 Internal Server Error" - and tells us that this is one more blog with a broken template.

I have, for a long time, recommended regular template backups , for those who like to tweak the template. Normal backup uses the "Backup" wizard, on the dashboard Template page. When backed up, an XML file, containing the template code, is extracted and saved locally. To restore, the "Restore" wizard is used and a previous Backup XML file selected. That's how Backup / Restore should work - but it isn't always that easy.

We're seeing a few reports from blog owners, in Blogger Help Forum: Get Help with an Issue , with blogs being inaccessible. My blog can't be seen at all, it just says error when I'm trying to open my blog. I also can't edit anything, like HTML or Template. When the blog is viewed, it will issue one of several bX codes. So far, I've identified bX-3o92c2, bX-ppgc07, bX-tqn3zr, bX-v2vqfh, bX-vg1g6a. When the blog is viewed, using an HTTP trace , the trace will terminate, showing an old friend. Error 500 Internal Server Error

We've seen a few reports, recently, in AdSense Help Forum: Blogger / Host Partners - and in Blogger Help Forum: Get Help with an Issue , that refer to a mysterious error condition. Error 500 "Internal Server Error". Blogger Support has been diagnosing this problem, for a while, using a series of bX codes - and the codes thrown by this condition seem to change, from day to day. The last time Blogger Support provided any description of the problem - or guidance how to solve the problem, they made general mention of "corrupt templates".