Skip to main content

Posts

Showing posts with the label bX-*00016

May 2007: The First 2 Weeks

This month started out with the termination of Old Blogger . And then the fun started. Problems which were carefully analysed, and aren't randomly experienced by all Bloggers. Very few have approached epidemic level proportions , but do have odd, non-random distribution. Several problems seem to be centered around Singnet in Singapore - Bloggers either directly paying for service from Singnet, or having ISPs that connect thru Singnet. This isn't the first time that Singnet has been involved. What is unique about Singnet, that it can cause misery to its customers so easily? How do we know that this weakness in Blogger - and that's what it is guys - a weakness - how do we know that this weakness won't be visited upon other Bloggers using other ISPs? Maybe any of us might be affected, at any time. Blogger needs to start telling us what is going on. But the Singnet problems aren't all that's disturbing us. From last month (and some time previous), we have the...

Could Not Connect To Blogger.Com - A Possible Workaround

One possible reason for the odd distribution of the well known pink warning Could not connect to Blogger.com. Saving and publishing may fail. or similarly Cannot View Webpage may be that it involves several different problems, coming together. It's possible that Pete Hopkins explains one of the problems as a side effect of the cookies generated by Blogger, some of which are used in post editor. Cookies are normally small and unassuming, but there's a bit of unusual behavior in that Blogger automatically saves the first few k of your post in a set of cookies as you're typing. That way, if your browser crashes you can use the "recover post" link to get at least the first part of it back. However, the side effect of using cookies in this way is that even though they're only being used (abused?) for local/offline storage, your browser will send the cookies with every request to a blogger.com server. This might explain why some Bloggers report temporary relief by...

Required field must not be blank

The typical problem report is I get this message at the top of the web pages when it doesn't work. We're sorry, but we are unable to complete your request. The following Errors were found: blogID: Required field must not be blank >> Since this is a post editor problem, and at least one instance of this problem also involved the Could Not Connect symptom , let's see if a possible workaround, provided by Pete Hopkins , has any use here. >> Blogger Employee has now become involved, in one scenario involving this error . >> Help us to help you. Check how you are logged in . Then, read more about the problem . >> Forum thread links: bX-*00037 >> Copy this tag: bX-*00037 >> Top

Could Not Connect To Blogger.Com - Help Diagnose This Problem

In my musings about the well known pink warning Could not connect to Blogger.com. Saving and publishing may fail. or similarly Cannot View Webpage I realised a lot of questions. I think we need some idea of the nature of this problem. The answers can only come from those suffering . Describe, for the record, all symptoms observed. What does "Cannot Connect To Blogger" / "Cannot Publish To Blogger" mean for you? Where are you located, geographically? What ISP do you have? What type of Internet service - Cable TV, Dialup, DSL, Satellite - do you have? What speed (down / up, if known)? How does your computer connect - Ethernet, WiFi - to your service? Do you have a broadband router? Have you ever tried Publishing, when the message is being displayed on your screen? If Yes, could you, ever, publish successfully? If not, precisely, what error or problem was presented to you? Do you have more than one browser? If so, Have both browsers ever shown the problem? Hav...

Could Not Connect To Blogger.Com

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