Showing posts with label Problems-Other. Show all posts
Showing posts with label Problems-Other. Show all posts

Friday, November 27, 2009

bX-qm5h6h



"can you help me with the bX-qm5h6h error? I would be very thanksful!"

This bx error code has been reported about because it has to do with people trying to export their old blog into a new one.

Here is what some others have posted about this particular bx error code:

"this infamous error code keeps appearing with an apology about server error every time I attempt to import from one blog to another....."

"I've been trying to import Bodge's Bulletin posts to the new blog but keep getting an error message "bX-qm5h6h" - anyone having the same problem?"

"The error code is bX-qm5h6h. I've tried clearing my cache and cookies as well as using a different browser. Nothing helps. Is Blogger aware of this problem?"

According to a posting on Twitter it seems as though this particular bx error code is a problem that has to do with Blogger.com itself and so far no solution from them has been posted online.

It also seems that this particular bx error code has been only posted about recently and since so many people have posted about it in a shourt amount of time it is possible that this could be a temporary bx error code problem. You should give it a few days to see if the problem solves itself (or if Blogger.com themselves solve it). You could also try using the bypass procedure to see if that will get rid of the problem.

Thursday, January 29, 2009

bX-igo1r0



someone posted that they tried to remove one of their registered mobile devices and could not complete their request.

Now I have to admit that this is a problem that I'm not familiar with since I don't have any mobile devices on my blog BUT the procedure is the same when you want to report a bx error code to Blogger.com!

Just click on the link that says "Report Your BX Error Code Problem" that is located on the right side of this blog and that will take you to a link where you can report your bx error code to Blogger.com.


Wednesday, October 1, 2008

bX-m6jgy3

someone posted that they got this bx error code after opening their dashboard and clicking on the "template" option / tab.

While this may be one of the "temporary" bx error codes that Blogger.com has talked about before - it is always a good idea to back-up a copy of your current blog's template!

Sunday, August 3, 2008

bX-a2ooj7



bX-a2ooj7



this bx error code came up when trying to update one's blog template

*A Blogger.com employee has said that when some of these bx error codes have to do with adding a new template, sometimes the template itself has some error in its html coding which means that Blogger.com can't accept it.

What do you do in such a case?

Well you'll have to go over the html coding of the template that you want to add and make sure that the html coding is correct and that it doesn't have any missing closing tags or any missing html coding.

If the html coding isn't completely correct then it won't be accepted as your new Blogger.com template



Tuesday, July 15, 2008

Comments From Others!

Here is a comment that was left by a blogger who has a blog on Blogger.com:

"I have tried and tried to contact Blogger.com but I have no idea how! I have started to move my site over to Wordpress. I thought that if Blogger was to smarten up I could continue with them. That has not happened."


Saturday, July 5, 2008

I Found Out The "Bypass" Procedure Solves Yet Another Blogger.com Problem!

Have you ever tried signing in to your Blogger.com account only to be met with the folowing error message:

Your browser's cookie functionality is disabled. Please enable JavaScript and cookies in order to use Blogger

Well I got this message today and decided to try and get out of it because I knew that something was wrong here because I have been able to get into my Blogger.com account before. So I tried the "bypass" and it worked!





August 17, 2007 - I got this same problem to day when I was trying to get to my blog and I used the bypass procedure and as you can see I'm back to my blog!