The Real Blogger Status

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 of bX codes, that are not solved by simply resetting the template - and do not involve the mysterious "500 Internal Server Error" . In some cases, the blog owner may see a bX code when trying to use "Configure Blog Posts", or another Layout gadget wizard. If the blog itself can be viewed, and Template HTML Editor is usable, the bX error may come from use of a "0" Alpha color setting. Blogger Engineering is aware of the problem, and has suggested that a fix is being developed. While we await the necessary fix, we may need to work around the 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".

One of the more irritating Blogger problem codes is seen a lot by people who use some versions of Internet Explorer (and oddly, by some users of Chrome and Firefox). I keep getting this, any ideas?? Whoops, that's an error! (bX-w7tr63) Recently, we see the suggestion, that there is an end in sight.

One subject of mystery, in Blogger lore, concerns the infamous "bX" codes . One forum personality, long ago, compiled a blog listing several hundred known codes, and their supposed "diagnoses" - and would later use the blog as a reference, when advising how to solve a given "bX problem". That same person showed complete lack of understanding, in a single sentence. It's disheartening to see that the bx error code problems are still existing. The "bX" codes are not problems - they are simply symptoms of problems , identified using a canonical code structure.

We have numerous blog owners report that they cannot access their Blogger dashboards. Every time I login to Blogger, I get We're sorry, but we were unable to complete your request. When reporting this error to Blogger Support or on the Blogger Help Group, please: Describe what you were doing when you got this error. Provide the following error code. bX-w7tr63 What should I do? The only answer here is to reply Don't use Internet Explorer V11.

Everybody who has owned or read a Blogger blog, for more than a week, surely knows about the infamous bX codes - and has probably asked how to fix one. Some people have fixed one - but immediately, seen another. Others have seen theirs go away, then later discovered that the blog is broken. Some folks see the errors as major problems, others minor annoyances . it's disheartening to see that the bx error code problems are still existing. Not everybody realises that the codes are not the problems - they are simply a method to identify the problems. Many Blogger problems cannot be identified easily in language.

Right now, we have several different problems, being reported in quantity, in Blogger Help Forum: Something Is Broken . Image / video upload. Stats, and the "Don't track your own pageviews" option. Some specific bX codes, and miscellaneous network issues. Recently, the problems with image and video uploads were reported to Blogger Support - and eventually, we got a monolithic response Use draft.blogger.com. In other cases, we've been told Stop using Draft Blogger! The contents of Draft Blogger, and its differences from Production Blogger varies, at the convenience of Blogger Engineering.

One of the most misunderstood features of Blogger blogs is the mysterious bX codes . Every day, we see the frustration It says there's something wrong and I should give this "error code" so Blogger can fix it. What should I do? Where can I send the "error code"?

We've been advising anxious blog owners, for some time, how to recover deleted pages and posts. The easiest solution, in the long run, is to recover the PageID / PostID , and re publish the deleted page / post. Unfortunately, all deleted pages and posts can't be edited and re published . With new posts, un indexed by the search engines, you won't be able to find the post in cache - and you'll never determine the PostID. This will be a frequent problem with deleted pages - as static pages generally won't get indexed by the search engines - nor will they ever be included in the blog posts feed. In some cases, even when you know the PageID or PostID, the page editor / post editor may simply reject your attempt to re edit - and give you another bX code. Even so, all is not lost. You may have to rebuild the page or post - but you can generally keep the URL, of the deleted page or post, operational. Just plan the rebuilding process.

We're seeing a number of problem reports, in Blogger Help Forum: Something Is Broken , about various problems which involve CAPTCHA verification processes. The symptoms are fairly diverse. Some blog owners report problems with commenting, on their blogs. Some report problems with high posting volumes. Some report problems getting abuse review requested, for their blogs falsely accused of hosting abusive content. The reporting volumes, and perceived urgency, for each case, will vary.

This month, we've seen more than a few reports, in Blogger Help Forum: Something Is Broken , about various Blogger dashboard problems. Both the Overview and Post Editor dashboard sections seem vulnerable to problems - typically described as bX code terminations . Many of the people reporting problems admit that they are using Internet Explorer V8. For some blog owners, the choice of staying with IE V8 is not an option. Get everyone to use Chrome, and don't support those using IE V8. Win XP works fine. Everyone can't get new computers or operating systems, every time some new software comes out! Unfortunately, Windows XP was sunsetted, by Microsoft, some time ago - and IE V8 is the last version of that browser that will run, on Windows XP. Windows XP and IE V8 may be "good enough" for now - but time is running out, on both.

We've been seeing a steady stream of problems being reported in Blogger Help Forum: Something Is Broken , from blog owners unable to use post editor. The symptoms are varied, in detail. Some can't get the cursor active, in the window. Others can't use the Preview option. Still others can't Publish. The primary symptom, seen by many, involves yet another mysterious bX code . In many cases, this problem has been forecast, for some time - and the blog owners should blame only themselves. Many of these blog owners are using - or trying to use - Internet Explorer V8, to maintain their blogs.

The New Blogger Interface has been available outside Draft Blogger for almost a year - and continues to provide traffic to Blogger Help Forum: Something Is Broken , with new problems, every month. One subject of problems appears to involve the Template "Edit HTML" wizard, and various bX errors issued when attempting to save changes made to the HTML code. The bX errors are very mysterious - and to those of us outside Blogger Engineering - almost monolithic. Recently, we've noted one possible affinity in the errors, involving blogs using templates developed outside Blogger / Google . I got a custom template for my blog, from TheCutestBlogonTheBlock. I followed all the directions to add the template to my blog, and copied everything correctly - but I keep getting a message that says Sorry, we are unable to complete your request advising me that I need to contact Blogger Support.

Now that support for "legacy" Blogger accounts (accounts created before 2005, without Google account association) ends after this month , blog owners are trying to catch up. Some blog owners are reporting that, when trying to use the "Forgot?" wizard , they are seeing bX-2uckqc Blogger Support has accepted responsibility of the problem, and announced yesterday We're investigating reports of users seeing bX errors when using the recovery form found at http://blogger.com/forgot.g (Update 10/13): This code has been resolved . I was finally able to recover my blogs. >> Top

We've seen a few reports today, in Blogger Help Forum: Something Is Broken , from blog owners who can't login, or load their dashboard. What does bX-1tj3ze mean?

I'm scared of elephants, if they're allowed to run wild. What time is it, when an elephant sits on the hood of your car? OK, Chuck, I'll bite - What time is it? Time to get a new car. LOL. Many years ago, when I moved to California, and having heard of the possible damage to your car (probably, an uninsured expense too) should an elephant sit on it, I put up a sign in my back yard. No Elephants Permitted Here! And, apparently the sign served its purpose - I haven't seen a single elephant in my back yard - or sitting on my car - since I moved here. An unlikely tale, you probably say. More crudely, you'd ask me What have you been drinking today, Chuck? So, what's the point of this narrative? Just this, that most bloggers may not waste time in putting up signs to keep elephants away - but they have other, stranger superstitions . My favourite examples of the latter would be advice from some bloggers about how to avoid the mysterious bX codes , the equal...