The Real Blogger Status

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

The ability to copy comments and posts into a blog - and even between blogs - is a useful option in Blogger. Some blog owners take the "Export Blog" / "Import Blog" wizards too casually. Most computer owners enjoy multitasking - and multitasking, between various online activities which involve your personal involvement, can increase productivity. The process of importing comments and posts, into a Blogger blog, does not involve your personal involvement - and does not work well during multitasking. Multitasking will actually slow the import process down - and what might take mere minutes can take hours, or days.

If you have a blog with multiple authors, you may have learned by now that you need to watch what's being posted. If there's lots of posting activity, though, you can't always check the blog - or even the newsfeeds from the blog - as often as you'd like, to see if something has been added. BlogSend saves you from that task, by simply notifying you ( or your designates ) when a post is added.

When publishing a post, or saving as Draft, some Bloggers are getting various error messages Invalid security token. or maybe securityToken : Your request could not be processed. Please try again. or similar messages No further details are typically provided by the Bloggers, and apparently there's no bX- code being issued with the error. I would bet that another scripting change was made recently, and the folks affected have cached script that's not compatible with their cookies. Apparently clearing cache and cookies is the proper solution - several Bloggers have acknowledged this solution in his/her case. Also suggest that the Blogger may need to verify how he (she) is logging in to Blogger.Com . >> Forum thread links: bX-*00015 >> Copy this tag: bX-*00015

When publishing a post, or saving as Draft, some Bloggers are getting various error messages Invalid security token. or maybe securityToken : Your request could not be processed. Please try again. or similar messages No further details are typically provided by Blogger Engineering - and apparently there's no bX- code being issued with the error. It's probably a variant of the " 403 Forbidden " error. I would bet that another scripting change was made recently, and the folks affected have cached script that's not compatible with their cookies. Apparently clearing cache and cookies is the proper solution - several Bloggers have acknowledged this solution in his/her case. Also suggest that the Blogger may need to verify how he (she) is logging in to Blogger.Com . (Update 2015): This symptom is now being reported as " Invalid Security Token Error 403 ".

This problem is Serious. It started maybe 15:00 PDT today, and 6 hours later, there are maybe 20 separate threads, many with multiple different Bloggers complaining. It is affecting both blogs with Classic templates, and with Layouts templates, though not consistently. Picture uploading is returning bX-gcdngf Additional information blogID: xxxxxxxxxxxxxxxxxxx uri: /upload-image.do host: www2.blogger.com The problem is not consistent! I managed to upload this to The Real Blogger Status - Beta (Layouts template). I got this error, though, when uploading to this blog (Classic template), and to Nitecruzr Test (Classic template) and to Nitecruzr Test New Template (Layouts template). It does not respond to clearing of cache and cookies (I tried twice). This may be one for Blogger Support to work on, and hopefully urgently . (Edit 3/14 17:00): Blogger has updated the problem , as Resolved . (Edit 3/14 9:00): Blogger has acknowledged the problem . We apologize for the trouble and a...