The Real Blogger Status

Some blog owners report a problem with editing posts, in post editor. With any changes made to a published post, an attempt to update shows another monolithic error. An error occurred while trying to save or publish your post. Please try again. But the mystery does not end there. Even seeing the error, a curious blog owner, refreshing the post as displayed, may find a surprise. Even with the mysterious error displayed, repeatedly, the changes just made may be visible in the post.

Recently, we've been seeing queries from some anxious blog owners Why should I have to sign out a total of three, four, or more times? With blogs that use a template that shows the navbar, the owner may logout, using the "Sign out" link - but the navbar may continue to suggest that they remain loggedin. This problem may start with how we connect to Blogger, as part of the mysterious Internet cloud .

Both the historically infamous "Another blog ..", and the currently infamous "Error 12", are part of the custom domain publishing process. Similar to the mysterious "bX" codes being an enhanced version of "We're sorry, but we were unable to complete your request.", "Error 12" (and variants) is an enhanced version of the monolithic "Another blog or Google Site is already using this address.". "Another blog" (which was generally seen during use of the Blogger Publishing wizard) is complemented by the equally annoying "Not found" (which is generally seen after Publishing is used).

We're seeing a problem with Blogger Hosted Comments - and "Bad Request Error 400", following the use of the comment "Preview" feature. When a blog owner or reader composes a long or important comment, use of the Preview feature is normal. Right now, after hitting "Publish", following a successful Preview, one frequently sees the bad news. Bad Request Error 400 There is a workaround for this annoyance - and it's not difficult to use.

One of the most obscure Blogger error messages - next to "Another blog ..." - is the monolithic advice seen on main page display of some blogs. No posts. or maybe There's nothing here! What can you say, to a blog owner who has started a new blog, and spent days publishing blog content - only to view the blog, and see "No posts." - or "There's nothing here!"?

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.

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".

We are seeing an increasing number of reports, in Blogger Help Forum: Get Help with an Issue , about problems accessing various dashboard features. Recently I have faced a problem on my blogs dashboard. The problem is Invalid Security Token Error 403 How do I solve this? This blog owner faces the latest variant of the long feared monolithic error, "403 Forbidden".

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.

Some blog owners, who use AdSense, received some very disturbing email this weekend. This morning I received the following email from Google. Dear Publisher, We have now verified that we are no longer detecting PII being passed to Google from the account(s) under your control. Thank you for helping to resolve this matter. Regards, The Google Policy Team What did I do, this time? Is my AdSense account in danger of being terminated? And the email was labeled "Policy Breach Notice". Fortunately, this was, apparently, just another episode of Google being Google .

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.

We're seeing an occasional report from blog owners, trying to access the Blogger dashboard, using Firefox. I am trying to update my blog, and I get an error WARNING UNRESPONSIVE SCRIPT A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue. I'm using Firefox, and I need help here! This has been a problem, for a few years - just a very low volume has been reported.

We've recently been seeing a number of reports, in Blogger Help Forum: Something Is Broken , from blog owners having problems with the "Create a new blog" wizard. When some of my students try to create a new blog, they get an error message The page you requested is invalid. These blog owners appear to be running up against new blog creation limits, possibly caused by Blogger prevention of abusive blog creation. Blogger has apparently added new ways of preventing abusive blog creation, by use of new activity limits.

Recently, we've been seeing a number of reports in Blogger Help Forum: Something Is Broken , from people suddenly unable to login to Blogger and maintain or publish their blogs. It appears that more and more private network owners are converting their email and office applications suites, to use Google Apps / Docs. This gives the various employers and schools the ability to block people, using their email, from also using extraneous / unnecessary services like Blogger and YouTube - and encourages the employees and students to spend their time more productively. People with Blogger accounts, that are based on the converted email domains, are seeing problems accessing their blogs.

Recently, we've been seeing a number of reports in Blogger Help Forum: Something Is Broken , from people suddenly unable to login to Blogger and maintain or publish their blogs. It appears that more and more private network owners are converting their email and office applications suites, to use Google Apps / Docs. This gives the various employers and schools the ability to block people, using their email, from also using extraneous / unnecessary services like Blogger and YouTube - and encourages the employees and students to spend their time more productively. People with Blogger accounts, that are based on the converted email domains, are seeing problems accessing their blogs.

Google has been providing single login access, to (almost all) Google services, for many years. Properly maintained, we can have one Google account, which lets us access all services, using one login. The single login approach is a convenience, when all of the services, which we use, are part of the same Google account. The single login approach becomes a challenge, when some of the services, which we use, are part of different Google accounts . As owners of Blogger blogs, there are some scenarios, where we have to deal with two different Google accounts simultaneously. Accessing non Blogger applications, like Google Apps . Recovering account / blog control . Transferring control of a blog . When we have to deal with two Google accounts, simultaneously, the single login approach becomes a problem.

We're seeing a number of blog owners, reporting a new problem with their Blogger dashboards, in Blogger Help Forum: Something Is Broken . I am seeing an new error in the Live Preview section of the Template Designer. The following errors were found: isExperimental : Required field must not be blank Upon examination of the URL window in the browser, the source of the problem is seen. draft.blogger.com /blogger.g?blogID=xxxxxxxxxxxxxxxxx#templatehtml It appears that we are seeing one more reason why routine use of Draft Blogger is not a good idea.

This week, we're seeing a few reports, in Blogger Help Forum: Something Is Broken from blog owners, trying to publish their blogs to custom domains. I'm trying to use the Publishing wizard - and I'm seeing a new error. This operation failed. Try again later. If the problem persist, please file a post on the help forum. What has Blogger changed, recently?