One of the reasons why Blogger code is so "unstable" (judging from the threads in the help forums) is that, as I wrote long ago, it involves code and data that starts on Blogger computers ("servers"), but is processed from other computers ("owned" by bloggers) which are connected to the Blogger computers over networks that nobody owns or controls.
Some of these factors Blogger can accept responsibility for. Others we (the blog owners, or blog readers) have to accept responsibility for. And still others are the fault of the network owners, and many of those are problems which nobody will accept responsibility for.
And that's the problem with diagnosing the ever common bX- codes. Of late, some bloggers are pumping themselves up, and declaring to the world
The frustrating part of this is that, in a very limited number of cases, clearing cache and cookies may produce positive results. But using that procedure as a general solution is so wrong, because it's limited to very specific scenarios. We need to understand the scenarios which generate the codes, before we can truly understand this.
>> Top
Some of these factors Blogger can accept responsibility for. Others we (the blog owners, or blog readers) have to accept responsibility for. And still others are the fault of the network owners, and many of those are problems which nobody will accept responsibility for.
And that's the problem with diagnosing the ever common bX- codes. Of late, some bloggers are pumping themselves up, and declaring to the world
Finally the solution to the BX error codes of blogger.comas if they themselves developed the simple process of clearing cache and cookies.
Don't know who and why it works and why google/ blogger have failed to recognize such simple tricks. But still that doesnt reduce its efficacy..
The frustrating part of this is that, in a very limited number of cases, clearing cache and cookies may produce positive results. But using that procedure as a general solution is so wrong, because it's limited to very specific scenarios. We need to understand the scenarios which generate the codes, before we can truly understand this.
>> Top
Comments
A bX code happens when there's an unexpected error on the Blogger backend. It can be any number of things, but the general pattern is that a bX code comes from an error that's probably rare enough that we don't have code to handle it gracefully. Instead, Blogger barfs, shows the bX code (which is like a fingerprint of the error, so we can look it up), and that's it.
Of course, sometimes situations arise where these very rare errors become common (a bug on our end, or some service we're dependent upon is undergoing maintenance) and are seen by lots of people. It's these cases that we have the http://bx-codes.blogspot.com/ blog for, which lets us instantly show a relevant error message on the bX code page, and any workarounds that may exist.
"Clearing cache and cookies" will almost never actually "solve" a bX code problem. The exact same effect would be achieved by just waiting a minute or so and re-trying.
Clearing cache and cookies helps with other problems, though, such as strange browser behavior when logging in, or a page not appearing or behaving correctly.
If you're faced with a bX code, and waiting and retrying doesn't work, my next recommendation would be to try and get more information (does this happen on other blogs? did you recently change your blog's template or settings?) and then see if people are talking about the bX code on the Blogger Help Group. If no one is, start up a new thread.
If you keep asking for a "solution", you are wasting everybody's time! There is no solution, because the codes are not a problem!