The Real Blogger Status

In my tutorials that instruct you how to make your blog friendly to search engines in general, and to the Google spider specifically, the meta tag is a key element. The meta tags are very versatile code that should be located immediately following the blog title, in the blog header. You'll be using the Template Editor to view, and to modify, this code. As always, if you intend to make changes to the code, backup the template before and after making changes.

On Mar 22, 9:43 am, (Name Has Been Omitted To Protect The Gullible) wrote: I'm seeing lots of login problems posts, so I wanted to share what worked for me to fix my problem. After migrating to new blogger, I could no longer get in. When I entered my id and password, I would just go in circles with a refresh, or sometimes a "click here to continue" link that didn't work. I went through all the blogger helps files and did everything they said to do. I also have McAfee, and thought that might be the problem I changed javascript settings, security settings, privacy settings, and made sure all the blogger.com URLs were in my allowed cookies. I turned McAfee off. Nothing worked. So finally, instead of adjusting security settings manually, I just reset everything with the reset button. I use Internet Explorer. Here's what worked for me: Choose Tools > Internet Options > Security Click "Custom Level" In "Reset Custom Level" choose medium and h...

I suspect that all Bloggers see this well known pink warning periodically. I don't think this is the fault of our Internet connections. This warning was up for a few seconds, while I printed this picture; then it, conveniently, went away. That doesn't happen all of the time. Many times, I am busy in the Post Editor, with the warning displayed. Even when I hit the Publish button, and I am seeing the normal status messages associated with the Publishing process, the warning remains. I've seen this when editing Classic Template blogs (this one, for instance), and when editing Layouts Template blogs (The Real Blogger Status - Beta, for instance). It's my impression that I see this more often during times when more people are posting in the forums, and presumably when more people are Blogging. As far as what does not help with this problem: Clearing cache and cookies does not help, consistently (though I will still suggest it as an initial diagnostic step). Using anothe...

This is not a Major Malfunction in volume - 18 threads over 2 weeks, with some folks posting into multiple threads. But there does seem to be a trend. And some Bloggers, who have been reporting the problem for over a week, are getting understandably angry. It is a Serious Problem to those Bloggers, and it is not going away. bX-qfealt Additional information blogID: nnnnnnnn uri: /posts.g host: www2.blogger.com (Edit 3/28): Blogger Employee claims Everything seems to be working fine on our end as Bloggers state It makes no difference on what operating system I log in on, what time of day etc.. I've tried different computers, clearing caches and restarting connections and computers - all the the same effect.. >> Forum search links: bX-qfealt >> Copy this tag: bX-qfealt

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