The Real Blogger Status

This one may be the problem of the week. We have Jordan's statement that they are "looking into it" , and that's it. That's a bug that you've caught, unfortunately. We're looking into it right now. >> Forum search links: bX-pn6gdm >> Top

How many people know what etiology is? Wikipedia defines it as ...the study of causation It's a fancy term for cause and effect. Fancy or not, though, it can have useful applications in real life. In the medical world, it might be used in a study of the spread of an epidemic. In computers, we might apply its principles for analysing a chronic network problem, as in deciding if multiple people, reporting the same symptoms, implies the existence of a major, widespread computer problem. Have you ever been to a hospital, and seen many sick people? If you did go to a hospital, would seeing the many sick people there lead you to conclude that there is a worldwide epidemic in progress? Most people are too analytical to lead to that conclusion. They know that a hospital is where sick people are expected to be seen. Oddly enough, though, many folks who wouldn't make an assumption about a medical epidemic, based upon being in a hospital, will visit a technical help forum,...

Lately, we've had a few folks complain about their blog, or parts of it, being in the wrong language. Sometimes, it's not even a foreign language, just "?" everywhere. There are several settings that you can make, which will have varying effects upon your web experience. Consider the effect of each setting, carefully. Some settings may be more relevant in the GUI Post Editor wizard , aka "Compose" mode.

Contending with the (apparently still active) bX-w12hpk for error of the week. Similar in reported volume too. This one appears to be related to the Login script. bX-v6uqpl Additional information uri: /loginz host: www2.blogger.com >> Forum search links: bX-v6uqpl >> Top

This may be the error code of the week. Low volume, but a steady stream of reports. No consistency of symptoms, other than the code itself. Two posts reporting missing images, but that's a random and well known problem anyway. Does seem to have an alias, bX-v6uqpl , with similar reporting pattern. bX-w12hpk Additional information uri: / host: xxxxxxx.blogspot.com >> Forum search links: bX-w12hpk >> Top

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

All of the companies that I've worked for in my history, which had computers, controlled everything rather tightly. Businesses do that. Businesses owned the big computers, aka mainframes. We, as programmers, would write code. We would test the code. We would give the code to a computer operator, who would run the code as a job. We would train the computer operators. All code ran on company owned and controlled computers, over company owned and controlled networks, maintained by company trained personnel. Every change was made, and tested, by people working for the company. Very tightly focused, and controlled.