Blogger Error Code Blog
If you have been on New Blogger for any time, you very likely at some point have run into an error. It happens. And New Blogger has introduced a new system of reporting those errors by giving each one it's own code. Yes, the dreaded bX- error codes. It can be frustrating.
But behind the scenes at the BloggerPlex, there is a blog apparently maintained by the Blogger Engineers that consists of known error codes, and when known what causes them. Trying to ease the frustration when the problem is known.
What happens, is if you get an error and it's not documented in this blog yet, you'll just get the somewhat cryptic and frustrating " We're sorry, but we were unable to complete your request" screen.
BTW, this one screen I generated isn't Bloggers fault. It's from going to the not-yet-live video preview page I hinted at in my previous post . Also it should be passed some parameters, which are unknown. So that page should error out right now.
But, if the error code given is known and documented at the bx-error code blog, then you'll get an additional message from the Blogger Engineers telling you what's up.
This error was artificially generated by me, but reflects the message for the bX-l9xjx9 code.
When the error page is generated, it uses a json call to the label feeds of the bx-blog for the generated code. Example for the bX-l9xjx9 code.
If that label exists, then the message attached to it is displayed. If the label doesn't exist, then it hasn't been documented and no additional information can be given.
It's a bit incestuous using a blog to report the errors on Blogger, but still a good idea if it can save someone even a little confusion. I guess the biggest problem is still the unknown errors that pop up. Those are always going to be frustrating no matter what.
But behind the scenes at the BloggerPlex, there is a blog apparently maintained by the Blogger Engineers that consists of known error codes, and when known what causes them. Trying to ease the frustration when the problem is known.
What happens, is if you get an error and it's not documented in this blog yet, you'll just get the somewhat cryptic and frustrating " We're sorry, but we were unable to complete your request" screen.
BTW, this one screen I generated isn't Bloggers fault. It's from going to the not-yet-live video preview page I hinted at in my previous post . Also it should be passed some parameters, which are unknown. So that page should error out right now.
But, if the error code given is known and documented at the bx-error code blog, then you'll get an additional message from the Blogger Engineers telling you what's up.
This error was artificially generated by me, but reflects the message for the bX-l9xjx9 code.
When the error page is generated, it uses a json call to the label feeds of the bx-blog for the generated code. Example for the bX-l9xjx9 code.
<script
src="http://bx-codes.blogspot.com/feeds/posts/default/-/bX-l9xjx9?alt=json-in-script&callback
=showErrorMessage" type="text/javascript"></script>
If that label exists, then the message attached to it is displayed. If the label doesn't exist, then it hasn't been documented and no additional information can be given.
It's a bit incestuous using a blog to report the errors on Blogger, but still a good idea if it can save someone even a little confusion. I guess the biggest problem is still the unknown errors that pop up. Those are always going to be frustrating no matter what.
Posts
Post a Comment
20 comments:
Here’s a question that struck me when I first read this:
"How can an error exist that the programmers don’t know about? Shouldn’t errors on an implemented system be known? Otherwise how is the system running?"
Now I’m kicking myself :P
This is some good detective work. Apart from being cool, it also shows us a cool way of using Blogger blogs as databases.
See where I’m going with this? }:)
Yes, you should kick yourself for that thought. :-)
And I agree it's a cool use of using Blogger blogs as a database. Which is why I found it interesting.
And could make for other interesting uses...I haven't come up with anything myself. But you can at least see the format.
Fab spot yet again, Kirk.
I'm sounding like a broken record, aren't I?
I know. For a change, let me offer you... tada....
Chocolate!
(Happy? :D)
And by the way, more seriously, in case it's of use I've added that URL to the search engine for Google blogs that I made earlier etc.
Happy Easter, Passover etc weekend!
I'll be happier when I get real chocolates, but it's a start.
And I'm not sure that adding that blog's url to your search engine will help. It won't hurt neither, but that blog has the noindex meta tag (apparently they don't want the public looking) so it probably won't be included in the search.
Is it Easter? I suppose it is. Happy all that to you as well. ;-)
@Aditya:
Priceless thinking aditya..
@P3:
man, where was this blog back in v2.0?...:P
imagine it, it would have been the blog from blogger with most posts ever....even more thant blogger status.. hehehe..
well, more post that such a blog would have been in a actually still needed Blog: Blogger Splog Reports..
:P
I think we got a message from Pete!
See what comes up when you click this now
http://www2.blogger.com/video-preview.g
Very funny.
Haha. Brilliant. See, I knew Pete & crew read your blog!
Should have checked about the noindex ta, but never mind, can't hurt.
Oh and you know what you need to do if you want real chocs! :D
hehehe.. ah that pete....next thing you know, they will add a disclaimer inside the code that will say:
P3-G-AFH!.
:P
Hey, eagle-eyes, I've even seen them, yes, on FTP ... and what I find is still called Old Blogger ... and you know what, I thought they were some kind of Safari javascript flap (WebKit is sooo much more cool, but then you cannot use tweaks) and ignored them.
Point being: Are comments supposed to be brief?
No, point being, am I supposed to hang around and report the error? Does this benefit mankind in some way?
You and Aditya get to scheming, it's amazing.
Of course you should report it Zo. For every error reported, Google makes a generous donation to the PLF (Possum Liberation Front) to help fight for free range 'possums.
Once you've tasted free range 'possum, caged factory 'possums just won't do.
Hi there. Nice blog, and I like the cloud tag hack.
I was wondering if you know of a hack to display post titles (in alphabetical order) in a drop-down list for a specific label (or labels, using 'OR')?
Something like this:
http://hoctro.blogspot.com/2006/12/killer-hack-contents-by-category.html
but a drop-down list, and not a flat list.
I've been looking for a hack like that as it'll be very useful for my blog, but haven't found one.
Please let me know if you are aware of such a hack, or feel like designing one :)
Thanks!
-Amit (upsidedownworld at gmail)
Hey,
Can I nick your calendar script and modify it for my personal use in my blog?
I don't mind if you do, but you may want to wait. It was always my intention to release the 'calendar' publicly. I have it up now to test some things out, and I need to clean up the code and the install before I do. I just have been lazy. :-) Hopefully sometime next week I'll have it done.
You can take it as it is now, but you'll be making things hard on yourself. The code is...ummm...ugly and confusing (to me) and there are a few minor bugs in it as is that I know how to fix, just haven't yet.
So for your own sanity, I would recommend waiting just a bit until I finish it off (Note, even when I finish it will still be confusing and ugly code...heh. I really got lost in this one. But it should be somewhat more manageable, hopefully)
Hi phydeaux3, I was just surfing by from annie's blog and your calendar is the perfect thing I have been searching for. In fact its even better! I was using this calendar script which worked perfect till I switched over to blogger beta -
http://www.philringnalda.com/archivescripts/calendar/
Ramani has a cool and very pretty one on his blog but I'm drooling after yours :)
I will be waiting patiently for your script. Thank you in advance for coming up with something like this!
Okay. I'll wait. I'm not in a hurry either. :)
The only thing I'm concerned about is the "hopefully" next week promise. :P
Fortunately now there is a way to bypass the error screen so that you can go work on your blog.
I've been telling people that they should ask blogger.com for the steps to bypass the error screen so that they can go back to working on their blog
I find that even though these error code notices can be annoying you should contact blogger to see if they will give you the information on how you can bypass the error screen altogether.
I haven't had any problems since!
I just know that they created such a blog. However, I still doubt that they will update it often. Thanks for sharing anyway, useful for me.
Post a Comment
0