Use Two Browsers, When Working With Multiple Google Accounts

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.

Frequently, when you request assistance with a problem which involves your Google account, we'll start by advising you to

Clear cache, cookies, and sessions (yes, all 3) - then restart the browser.

This advice is neither ceremonial, nor pedantic - it's practical. And, it solves more problems than you would believe.

That simple advice works - because many problems are caused by the Google account login cookie, which is used to retain login status from application to application, within the various Google services which we may use. This is how Google provides single login to their various services.

That simple advice works best when we care only about the Google service immediately visible - and it requires careful maintenance of cookies filters. In cases where two services - or two Google accounts - are involved, you'd need to switch between account / service, rapidly and repeatedly. Rapidly logging out of one account, to login to another account, is both exhausting and technically unsafe.

Rapidly logging out then back in, to various Google accounts, creates odd symptoms, like the well known monolithic error

You have logged out from another location. Do you want to log in again?

Who among us has been able to correctly answer this simple query properly, without undue rise in blood pressure?

Another problem with clearing cookies, routinely, is that not all browsers allow selective clearing of cookies. Many have observed problems with non Google websites, after solving a Google problem which involves

Clear cache, cookies, and sessions (yes, all 3) - then restart the browser.

Yes, there are websites outside the Googlesphere!

If we need to work with two Google accounts, simultaneously, the only safe technique is to use two browsers, simultaneously. Since the Google login cookie is created separately, in each different browser, use of two browsers lets us maintain two Google sessions, simultaneously, without interaction between the two.

Since no two browsers are alike, we know realistically, that using two different browsers should not be done routinely. Many blog owners have a most favourite, and a least favourite, browser - and won't willingly use a different browser except when absolutely necessary.

Fortunately, many modern browsers, to retain their own customer base, allow for multiple sessions - where cookies and other preferences and settings can be maintained separately. Chrome has the "Incognito Window", and Firefox has "Private Browsing" - both of which let you, temporarily, setup a second browser session, with separate cookies, preferences, and settings.

In most cases, then - and if you are using Chrome or Firefox - when we advise you to

Clear cache, cookies, and sessions (yes, all 3) - then restart the browser.

you should be able to, alternately,

Activate a second browser session, when you are not currently using a second session.

In cases where you are currently using a second browser session, the advice would be more correctly phrased

Close the current second browser session, then start a new second browser session.

This advice would flush all current cookies, preferences, and settings which could possibly involve multiple Google accounts, and avoid various problems with Blogger and non Blogger applications.

>> Top

Various Problems With Blog Owners Using Internet Explorer V11

We're seeing a few browser related problems, possibly related to a recent update of Microsoft Windows and Internet Explorer, reported in Blogger Help Forum: Something Is Broken.

I can't see my dashboard!

and

I can't upload pictures - all that I get is a blank box!

and

I am receiving messages, when I log in, that my Internet Explorer is not compatible with Blogger.

Too many blog owners use Internet Explorer for using Blogger - and automatically accept updates, applied by Windows Update.

Right now, Blogger Engineering is in the process of updating Blogger to work with Internet Explorer V11. This is not a minor task - with all of the many Blogger features required by the various blog owners and readers, all of which must be checked for compatibility with each new browser version.

The recent updates of Microsoft Windows, to use Internet Explorer V11, is causing various problems to blog owners and readers.

Blogger Engineering cannot update Blogger, immediately, to work with the new version. While we wait for Blogger to be updated, it's possible that the Microsoft "Compatibility View" setting can help us bypass some of the problems.

• From the Internet Explorer menu, select "Tools" - "Compatibility View Settings".
• From the Internet Explorer address bar, click on the "broken page" icon.
• Type "blogger.com" into "Add this website". Hit "Add", then "Close".

If we can't use "Compatibility Views" to work around the current problem, we have to wait, patiently, until Internet Explorer V11 can be supported, by Blogger.

If we can't wait patiently, we may need to try using another browser with Blogger - at least to diagnose the problem at hand.

>> Top

All Mobile Computers Are Not Created Equal

We've seen a few questions about comments, supposedly published - but vanishing, when using a mobile computer, in Blogger Help Forum: Something Is Broken.

This symptom, as reported, reminds us of the long ago reports of "vanishing comments" - but using desktop computers.

At least one of the folks who isn't able to comment said she was attempting to do so from her mobile phone. Is Blogger now losing comments from mobile devices?

The answer here is not quite so ominous, though the situation is still frustrating - to both the blog owner, and the various visitors.

Blogger comments are offered in three "desktop" computer styles, selected by the blog owner.

• Embedded, positioned below the posts.
• Full screen, on a separate page.
• Popup, in a separate, miniature window.

Each of these choices have their own special advantages and disadvantages, which vary in relevance, according to the blog reader population.

On a "mobile" computer - and with the "mobile" template enabled, there is yet a fourth style.

• Embedded, in a special "mobile" dialogue.

The comment entry process, in general, involves at least four distinct steps.

• Authentication. Where required by the blog owner, and / or preferred by the blog visitor, the visitor may provide personal identification.
• Entry. The comment is entered, and edited.
• Preview. The visitor can view the comment, as entered, before actually publishing it.
• Verification. Where required by the blog owner, the visitor solves a puzzle, aka "CAPTCHA", to prove that he/she is not using an automated script.

Entry and Preview goes back and forth, at the preference of the comment publisher, until satisfied.

Depending upon the "mobile" computer and template in use, any of the four comment entry styles may be a problem, for any of the four steps identified. If you are familiar with the comment entry process, in general, consider the various controls and objects involved - and when each object is presented to the visitor, attempting to publish a comment.

Consider three different possible ways of presenting the various controls and objects, involved in publishing comments.

• Everything "visible" simultaneously, with the display zoomed out so everything is visible. On anything but a large screen tablet, you would probably need a magnifying glass, to read the captions, instructions, and labels.
• Everything "visible" simultaneously, but with most objects off screen, until each is needed. Scrolling is done using finger gestures, not using scroll tabs - and it's never obvious where any "missing" objects may be, at any time.
• Everything visible in sequence, one step at a time. Extra controls, to move forward and backward in the sequence, are required. To someone not familiar with the comment entry process, in general, some controls may not be obvious.

None of these three options provide perfect solutions. Even being experienced in the commenting process, I have found no obvious excellent choice, when using a "mobile" computer.

Besides the various control and display issues discussed above, consider the effects of cookies and scripts, which may or may not be supported by any given "mobile" computer - and layered security, which is a challenge, on every computer. Both may be a special problem, on "mobile" computers.

Until "mobile" computers are developed, with controls and displays equal to (better than) to those of "desktop" computers, I suspect that there will always be problems with commenting on "mobile" computers - just as there are problems with use of "mobile" computers, and with commenting on all computers, in general.

>> Top

Diagnose Problems Using Differential Testing

Sometimes, you may find yourself reporting a problem, in Blogger Help Forum: Something Is Broken - and observe that nobody else has the same problem.

If there's any normal problem activity in the forum, you might find yourself waiting - in vain - for an immediate answer to your problem report. While you wait for advice, why not do some basic analysis of your problem?

A differential test set of your problem, based on some reasonably basic details, can help you see where many problems may originate.

Sometimes, you can identify the basic source of your problem - or at least, offer some ideas to a forum helper.

Similar to affinity testing, differential testing can be a big help when you have a problem. Here are a few simple differentials, which you can perform, with a little determination and planning.

1. Account. Use a different Blogger account, and try the same procedures against your blog.
2. Blog. Setup a different blog, and try the same features and procedures on the other blog.
3. Browser. Use a different browser, and try the same procedures on your blog.
4. Computer. Use a different computer, and try the same procedures on your blog.
5. Connection. Use this browser / computer from a different Internet connection - or use a different computer which uses a different Internet connection - and try the same procedures on your blog.
6. Logout. Logout from Blogger completely, when diagnosing a problem that involves viewing the published blog.
7. Posts. Identify the last few posts, published before you first observed the problems. Edit those posts, and save them as Draft copies.
8. Template. Change the blog, to use a different template.

Maybe, you can think of still more differential tests.

By changing exactly one significant detail at a time, and carefully observing the result of the change, you can at least get an idea what actions which you may have made, to contribute to the problem.

Use a different Blogger account, to maintain / publish your blog. As an alternative, first clear cache, cookies, and sessions (yes, all 3, in this case!), then restart the browser. A second alternative would be to use an "incognito" / "private browsing" window, in this browser. Both alternatives may complement each other, when used simultaneously.

Set up a different blog, with similar features / content. As an alternative, ensure that your blog uses a standard Blogger template - then reset the post template, and remove any shiny third party accessories. Note that all problem third party code may not have been recently installed - but may still cause problems.

Use a different browser, to maintain / publish your blog. As an alternative, ensure that you have the latest browser update - then disable all add-ons and extensions, in this browser. The "incognito" / "private browsing" window may be useful, in this case also.

Use a different computer, to maintain / publish your blog. As an alternative, check (and update) all cookie and script filters, on this browser / computer.

Use a different Internet connection, to maintain / publish your blog. As an alternative, try changing your Internet address - if your ISP will permit this.

For problems which involve viewing the published blog, logout completely from Blogger. As an alternative, first clear cache, cookies, and sessions (yes, all 3, in this case!), then restart the browser. A second alternative would be to use an "incognito" / "private browsing" window, in this browser. In this case, all three alternatives may complement each other, when used simultaneously.

Remove any recently published posts, from the blog. As an alternative to deleting your recent work, edit each questionable post and save it as draft.

Use a different template, on this blog. After changing the blog template, remember to reset the post template. As an alternative, reset all gadgets and the post template. If you're using a custom, third party template, update to a Blogger standard.

If you have any experience with Blogger problem analysis and resolution, you'll note that none of the alternatives, suggested above, will create the full effect of the specific differential. However, each alternative will give you a partial differential - if the complete change is not convenient.

Many Blogger problems start with you - and can best be reproduced by you. That being the case, it's best that you try to reproduce the problems (or "bX codes"), through a differential analysis - and observe the results of your tests.

The best idea here is to try at least 2 differentials.

• Make one change at a time.
• Observe the results of each change, separately.

If you try a different browser - and magically the problem goes away, you're good - for right now. But what happens next week, if you experience a different problem? Do you want to try a third browser?

How many browsers can you use - and break - before running out of browsers, that you like? Using a second or third differential, now, may help you more precisely identify the cause of the problem - and that's when you are more likely to get the attention of Blogger Engineering.

It's a lot more useful to diagnose a problem, with you carefully making changes, and observing what happens, then it is for you to report

I can't see my blog!

and get the reply

Your blog is fine!

High level (differential) testing can go a long way, towards getting a problem identified - and possibly, resolved.

>> Top

Windows XP / IE V8 Is "Good Enough" - But For How Long?

This month, we've seen more than a few reports, in Blogger Help Forum: Something Is Broken, about various Blogger dashboard problems.

Both the Overview and Post Editor dashboard sections seem vulnerable to problems - typically described as bX code terminations. Many of the people reporting problems admit that they are using Internet Explorer V8.

For some blog owners, the choice of staying with IE V8 is not an option.

Get everyone to use Chrome, and don't support those using IE V8. Win XP works fine. Everyone can't get new computers or operating systems, every time some new software comes out!

Unfortunately, Windows XP was sunsetted, by Microsoft, some time ago - and IE V8 is the last version of that browser that will run, on Windows XP.

Windows XP and IE V8 may be "good enough" for now - but time is running out, on both.

Blogger, like every website on the Internet, is going to design their displays and wizards - such as Post Editor - to use features provided in the newer browsers.

As Blogger fixes problems, like the recent problem with the Post Title, the more browser versions they have to support, the more complex their code becomes. Besides fixing problems with Post Editor, Blogger will be developing new features - like Google+ Comments, and the recently added "Blog Posts" option to "Show Author Profile Below Post".

Each of these changes - the recent Post Editor fix, Google+ Comments, and the new "Blog Posts" option - must include code to work in all supported browsers. The more browsers supported, the more complex the Blogger code becomes.

Owners of older computers, with less bandwidth and memory resources, are going to notice Blogger - and other websites - requiring more resources. As the Blogger code base becomes more complex, the amount of code required will make the increased resource use more obvious. Many people have already noticed Blogger running slower, when they edit their posts.

As Blogger code becomes more complex, and as they support more browsers, it's going to take them longer to develop new features - and to fix problems with current features.

The only answer here is that Blogger simply can't support an infinite number of older browsers. As newer browsers, with newer features, are made available, they have to stop supporting older browsers.

It's possible that Blogger is currently making an effort to temporarily override their earlier stated browser support policy, so they can accommodate Windows XP and Internet Explorer V8 - but it's unlikely that they can do this, forever.

If Blogger fixes the current flood of bX code errors, for users of IE V8, this may not last, for long.

>> Top

Post Editor Problems With Blog Owners Using Internet Explorer V8

We've been seeing a steady stream of problems being reported in Blogger Help Forum: Something Is Broken, from blog owners unable to use post editor.

The symptoms are varied, in detail.

• Some can't get the cursor active, in the window.
• Others can't use the Preview option.
• Still others can't Publish.

The primary symptom, seen by many, involves yet another mysterious bX code.

In many cases, this problem has been forecast, for some time - and the blog owners should blame only themselves. Many of these blog owners are using - or trying to use - Internet Explorer V8, to maintain their blogs.

Last year, Google warned us that this time was coming.

We support the latest version of Google Chrome (which automatically updates whenever it detects that a new version of the browser is available). We support the current and previous major releases of Firefox, Internet Explorer, and Safari on a rolling basis. Each time a new version is released, we begin supporting that version and stop supporting the third most recent version.

Google stopped supporting Internet Explorer V8, in 2012.

As previously announced, Internet Explorer 10 launched on October 26, 2012, and as a result, we discontinued support for Internet Explorer 8 on November 15.

Recently, as part of an update to post editor, Blogger used code which is incompatible with Internet Explorer V8. As they continue to update Blogger, to remain compatible with newer browsers, they will continue this policy.

As time progresses, more blog owners, trying to use IE V8, will find problems with Blogger - with the problems not answered by Blogger Support. Blog owners using IE V9 or V10, in compatibility mode, will also see these problems.

If you are using Internet Explorer V8, you are way overdue for a browser upgrade. If your computer uses Windows XP, then you need to replace or update your computer. As an alternative, consider using Chrome or Firefox for all Blogger activity.

The solution, for this problem, requires your action.

>> Top

When Using Template "Edit HTML", The Edit Window Remains Blank

Since Blogger released their improved Template Editor, blog owners have been reporting a new, transient problem.

I click on "Edit HTML", and the editing display opens - but the HTML window remains blank.

Generally, you may wait a few seconds, and the HTML window will fill with the content. With enough patience, you'll see the content arrive - eventually.

Unfortunately, waiting won't always provide a solution.

Sometimes, you see the Template Editor display open, with a blank HTML window - and you wait patiently, with no result.

With the Template Editor display (common to every blog, and requiring no security) - and the Template HTML (unique to every blog, and requiring security) - coming from different servers - there's always the possibility that a dropped connection, from the Template HTML server, may cause the browser to time out.

In many cases, this will be a transient error. All that you need to do is to refresh the display.

• Try a browser refresh. F5, or maybe Shift - F5, forces a refresh, in most browsers.
• Restart the Template Editor. Click on Template, then "Edit HTML", again.
• In extreme cases, clear cache, cookies, and authenticated sessions (since this is secure content, you'll need a new authenticated session) - then restart the browser, and start over.

If the lost connection is not transient, your Internet service may be part of the problem. If a simple refresh does not solve the problem for you, you may want to look at the MTU setting, on your computer.

An overly ambitious Maximum MTU setting could cause a chronic or persistent dropped connection, with the Template HTML server. Lowering the Max MTU setting could resolve this symptom.

>> Top

Blogger And Mobile Computers

Using the term "mobile computer" is an example of the challenges involved, in using this variety of computer.

Even identifying this device, which is present in so many different manifestations, is confusing.

• Mobile Computer.
• Mobile WiFi device.
• Personal Digital Assistant.
• Pocket phone.
• Smart Phone.
• Tablet.

As the use of mobile computers becomes more common, we're seeing more and more problem reports and questions, from people unable to use Blogger.

• Some folks would like to maintain and publish their own blog.
• Others would like to post comments to their friends blogs.
• And still others don't understand why all of the various gadgets on their blog don't work for their friends, who are also using their own mobile computers.

One of the challenges of mobile computers involves the use of smaller displays, and the need to simplify the content displayed. This requires the use of special browsers and templates, which are designed to accommodate the limitations. The need to support additional browsers and templates creates more work for Blogger Engineering, who now has more different products to support.

Also, many mobile computers are designed to work over proprietary networks, provided by various "phone" companies. Blogger has traditionally supported use of alternate services - email, and SMS - for publishing posts to their blogs.

All of these differences create complexity, and additional possibilities for failure. And we see more problem reports, attributed to use of "mobile" computers.

Full function ("desktop" / "laptop") computers have challenges - but they are still easier to use.

We know about the different major browser brands, and the differences created by the use of each browser, on our desktop and laptop computers.

Chrome, Firefox, Internet Explorer, Opera, Safari all have their various peculiarities. These differences are multiplied, when considering the issues involved in developing new features - and in keeping up with new browser versions, and continually updating the various Blogger features and wizards, when required.

Besides the various different browsers, we have to consider the different activities involved in using Blogger. Browsing blog posts, browsing comments, publishing comments, maintaining the blog, and publishing posts, are all different activities - and have their own different needs.

The relative lack of limitations in "desktop" / "laptop" computers still makes each different activity simpler for the blog owner or reader. The process of developing and supporting the different Blogger features is easier for Blogger Engineering. These differences are not so transparent, when using a "mobile" computer.

Mobile computers have known limitations.

• Reduced display size.
• Reduced display colour depth.
• Reduced processor speed.
• Lack of various system features and utilities.
• Lack of a physical keyboard.

All of these details require mobile browsers and templates which operate differently, and the various Blogger features and processes must be used differently.

Try performing the various tasks identified above, using your desktop and mobile computer - and observe the differences. You'll quickly realise the differences, when browsing blog posts, browsing comments, publishing comments, publishing posts, and maintaining your own blog.

One of the workarounds, used by Blogger, to deal with the reduced functionality of a mobile browser / computer, is the "mobile" template. The mobile template, which is optional for all modern Blogger blogs, displays only text and pictures - and eliminates the many accessories, gadgets, and shiny formatting which may be seen in any blog with a "normal" template.

The different layouts of the posts and comments, on a mobile template, makes posting comments a different experience - and the lack of the various gadgets will produce different visitor activity.

The differences between the various "desktop" browsers are considerably less noticeable than the differences between some "mobile" browsers and computers. Most desktop computers use 3 different operating systems.

• Apple / Macintosh.
• Linux / Unix.
• Microsoft Windows.

Even with the different operating systems, the realities of marketplace competition creates some interoperability between the different desktop operating systems - and the different browsers are similarly common in design.

The better known mobile computers also have 3 major different operating systems.

• Android.
• Apple/iOS.
• Microsoft Windows.

Not all PDAs and smart phones use the standard 3 operating systems, however - some use proprietary browsers and operating systems, unique to the manufacturers. And the proprietary networks, provided by the different phone companies, further reduce the possibility of interoperability.

Lack of interoperability is going to create differences in how well different applications, such as Blogger, operate on the different mobile computers. These differences will be more significant than the differences created by the various "desktop" browsers, and operating systems - and we'll see more complaints from blog owners who can't use Blogger on their tablet, or whose readers can't post comments, using their smart phones.

Increasingly common use of multimedia content (both music and video) on mobile computers - combined with the lack of consistent support for cookies and scripts (and possibly, filtering of cookies and scripts) - will make availability of content differ, from computer to computer. Another problem here is lack of consistent support for the Adobe Flash product - which makes some YouTube content non playable, on some mobile computers.

Also consider the various security issues which may be different with mobile computers. Both the different security threats, and the different protective features, will make secure use of mobile computers a challenge - particularly when carried in public.

Fortunately, as mobile computers benefit from ongoing technological advances, improved design of mobile computers may make some limitations less significant. Improved displays, operating systems, and additional security devices are all coming.

As people buy and use more mobile computers, the differences between "desktop" and "mobile" computers will narrow. And use of different new desktop and mobile features, like innovative computer desktops, and products like Google Glass, will force desktop, laptop, and mobile computers to converge in functionality.

>> Top

We Are At The Mercy Of Every Anti-Malware Protection Program Imaginable

We see reports, from time to time, in Blogger Help Forum: Something Is Broken, about blogs which people can't read, from their computers.

One of my readers claims that I have a virus on my blog. He provided the following information:

AVG anti-virus detected the following threat on the site:

File Name: www.mydomain.com/favicon.ico

Threatname: Exploit Black Hole Exploit Kit

How do I fix this?

Similar to the many reports that we process here, about spurious spam classification, the above report is frequently determined to be a false positive. An anti-virus alert, even if a false positive, is generally not as simple to resolve as a spurious Blogger spam classification, though.

One of the frustrating problems with false malware alerts is that they come from so many different anti-malware products.

I've contributed my opinion about computers, and the suggestion that no two privately owned computers are identical, many times. One way which many computers vary is the complement of security software, which is chosen by each different computer owner.

At any time, any different anti-malware product may decide that some component of your blog is unsafe.

• Maybe, a single file mentioned in your blog code (as above, "favicon.ico") is suspect.
• Maybe, content hosted by "blogspot.com" is unsafe.
• The code may be an accessory that we added, intentionally.
• The code may be content in another blog - hosted by your blog in a bloglist, a linklist, or maybe in the Reading List on your dashboard.

In either case, you (or your reader) won't be allowed to view the blog - or may be allowed to view the blog, but given a stern warning which very few chose to accept.

Like many problems with layered security, any malware detection can come from

• A native browser filter.
• A filter in a browser add-on.
• A filter installed on the computer.
• A filter in a network appliance.

Listen to your computer. some time. Your anti-virus protection may update automatically - and may audibly announce the update. On a typical day, I hear the Avast client on my several computers announce an update, several times - and I am not (contrary to some misconceptions) seated in front of my computer on a 24 x 7 basis.

Avast (my personally and professionally recommended choice, to many people) is only one of dozens of various anti-malware products which receives automatic updates, when the host computer is online. Any one of these products may be updated, at any time -and somebody's access to your blog (or my blog) becomes blocked.

If you get a message from one of your would be readers

I can't view your blog!

this could be someone reporting that your blog just went offline, for one reason or another - or it can be someone just discovering that the anti-malware program, on his computer, has decided that BlogSpot hosted content is unsafe. In either case, there is not a lot that you can do, except wait it out - and concentrate on the readers who can access your blog.

>> Top

Would Be Blog Owners Report Inability To Create A Blog

We are currently seeing frustration, in Blogger Help Forum: Something Is Broken, about new blog creation.

Would be new blog owners have various concerns

I can't create a blog - the "Create" button is grey (inoperative)!

or

It keeps saying

Verifying availability

when I enter a blog name!!

or even

It said

This blog address is available.

until I hit "Create blog!" - then it changed to

Sorry, this blog address is not available.

Each of these problem reports - and others - may come from people who don't read the instructions, for using the wizard. Alternately, some folks may be complaining about yet one more case of over done layered security.

The most obvious problems, in the blog creation process, come from people who don't understand how to use the "Create a blog" wizard.

Not every would be blog owner understands that 3 things must be done, to make the "Create blog!" button operative - and all 4 must be done, before the blog is actually created.

1. Enter a Title for the blog.
2. Enter an acceptable and available Name for the blog.
3. Select a Template for the blog.
4. Hit "Create blog!", with "This blog address is available." displayed.

When you choose a Name (aka "address" or "URL"), enter your choice properly.

• Only enter the "xxxxxxx" part of "xxxxxxx.blogspot.com".
• Only use lower case alphabetic characters ("a" - "z"), numeric characters ("0" - "9"), and dashes ("-").
• Do not use a trailing dash (You cannot publish "xxxxxxx- . blogspot . com").

Besides the syntax issues when entering a blog name (URL), there is the unfortunate issue of competition in the creation process. Blog owners who are anxiously creating a new blog, based upon a current event - maybe a popular movie star, or an important political campaign - will be dismayed to see

Sorry, this blog address is not available.

If you are competing in real time, with other would be blog owners, for the name of your choice - and you take too long between Steps #1 - #3, and Step #4 - you may still see

Sorry, this blog address is not available.

Many people want to setup a blog, based on that blog name. Some may see the bad news, repeatedly, leading to one frequently seen complaint.

All the good addresses are taken!

And sometimes, to a more imaginative suggestion.

How do I get Blogger to re issue me the dormant address?

The latter question is one of futility.

Finally, the anxious blog owner may see

Checking address availability

for some time - possibly forever - if an overly ambitious cookie / script filter, or an intrusive security add-on is installed in the browser. In this case, the magical advice to

Clear cache and cookies!

or

Try a different browser!!

will be effective - though absent any attempt to diagnose the problem, one may not ever know what actual underlying problem may have caused the plaintive cry

I can't create my blog!

>> Top

Some Blog Owners Reporting The Template Designer Changes Do Not Update On Their Blogs

For several weeks, we're been seeing various reports in Blogger Help Forum: Something Is Broken, mentioning problems with template updates, being made using the Template Designer wizard.

The reports are not so widespread to indicate a complete malfunction - but neither can we dismiss the problem, as being unique to one browser, one template type, or one particular update pattern.

It's likely that we are looking at a number of problems, aggregated and compounded, into one common symptom.

I cannot Save changes in Template Designer.

With a problem report like this, some examining of the details may be appropriate.

The Template Designer wizard, which is a component in the Blogger Dashboard, is a complex and sophisticated collection of menus and utilities, which runs on the blog owners computers.

Like most Blogger code, the Template Designer is subject to the effects of other programs, and various security settings - which may be installed or set on each individual computer, with or without the understanding of the blog owner and / or computer owner. In some cases, the blog owner and computer owner may be different people.

If you are seeing a problem with the Template Designer, when trying to update the layout on your blog, there are several tests which you can make, which may help to isolate the problem.

• Try making the same updates, using another computer.
• Try making the same updates, using another browser on your current computer.
• Try setting up a new blog, with the same template, and make the same updates to the new blog.

If you're able to make one or more of the above alternate updates, that will help to eliminate some, or many, alternate suspects, as the cause of your problem. If other people are reporting this problem, their results from the above tests may or may not correspond with yours - because their base problem may differ from yours.

Right now, we're seeing seven different causes of these problems.

1. Changes made by Blogger Engineering, to support new browser versions and browser updates, and to provide new template features.
2. Changes inherent in new browser versions, made by the browser vendors.
3. Third party browser add-ons, installed by the owners of the various computers.
4. Security settings, inherent in new browser versions and third party add-ons.
5. The cumulative effects of various template tweaks, both made using "Edit HTML" and the Template Designer itself.
6. Unrealistic expectations of blog owners, about effects of Template Designer settings, against all templates provided by Blogger.
7. Unrealistic expectations of blog owners, about effects of Template Designer settings, against templates not provided by Blogger.

Of these possible causes, only #1 (and possibly #2 and #6) are the sole responsibility of Blogger Engineering. The blog owners (and computer owners) must assume some partial responsibility for #2 - and sole responsibility for #3, #4, and #5. The blog owner, and the developer of any custom, third party template, must jointly assume responsibility for #7.

Recently, Blogger Support acknowledged the problem, in part.

Some users have reported that the Apply to Blog button in the Template Designer is non-functional for some Dynamic View templates.

We also have a Rollup Discussion, in Blogger Help Forum: Something Is Broken, where individual details are being provided by various blog owners.

Right now, we're starting to suspect that some "problems" are actually caused by the blog owners, who are simply not aware that not all changes made, using the Template Designer (or the Layout or Template "Edit HTML" wizards), are designed to update all templates used in viewing our blogs.

>> Top

Disable The Mobile Template, On Your Blog - As A Default View

Over a year ago, Blogger introduced a useful template option for our blogs - mobile templates.

Blogger mobile templates are mobile-optimized versions of our Template Designer templates. If you are using one of these templates, when you enable the mobile template option your blog will begin rendering using the mobile version of the same variant. Even if you are not using a Template Designer template, or using a heavily-customized version of one, you can still enable this feature to have your blog start rendering in a generic default mobile template that we have created.

The mobile templates let computers with lower display size / resolution - aka PDAs, mobile phones, and smart phones - display the content of our blogs, without the unnecessary overhead which may be a part of our normal blog formatting.

If you are viewing this post on your smart phone, it's likely that you are viewing it using a mobile template. As exciting as the mobile templates are, however, they will not replace the normal, full feature templates - on every blog, or on every mobile computer.

Not every blog owner, nor every visitor, wants to view any given blog using a mobile template. Some tablet computers have display units which rival normal desktop displays from a few years ago - and low feature, mobile templates are unnecessary. Fortunately, there are a number of options - for the blog owner, and for the blog visitor.

If you are a blog owner, you can disable the mobile template, as a default, for your blog. For those blog owners who have forgotten how they set the mobile template on their blog, you use the "Template - Choose mobile template" wizard, from the gear icon beneath Template - Mobile. Simply select "No. Show desktop template on mobile devices.", and Save - and that's it.

If your blog has a Classic Template, you can disable the default mobile template from your blog, with a little extra bit of effort.

1. Start with the Template wizard, and select "Upgrade template".
2. Once your blog has an upgraded template, you can use the "Choose mobile template" wizard, and select "No.".
3. Go back to the Template wizard, and at the bottom find "Revert to classic templates".
4. Selecting the latter link, your blog will be back to the previous, Classic template.
5. But now, the default Mobile template will be disabled.

Upgrade your blog, to a Designer template.

Return your blog, to a Classic template.

Having set - or un set - the default mobile template for your blog, your visitors have the final say, how they want to view your blog. If you are the visitor, you can choose, with a little effort.

Any time you are viewing a Blogger blog, from any computer, you can select - or de select - the mobile template for the blog which you are viewing. Just use the appropriate mobile template URL suffix.

• To de select the mobile template, use "/?m=0". http://blogging.nitecruzr.net/?m=0
• To select the mobile template, use "/?m=1". http://blogging.nitecruzr.net/?m=1

You can view a blog using a mobile template on your desktop computer - or a blog using a full feature template on your mobile computer. It's now your choice.

This blog, viewed from this computer, using a Mobile template.
Unfortunately, it's your choice, when you use your mobile computer, only. You have only two choices, for your blog.

• Don't enable the mobile template.
• Enable the mobile template.

Each of your readers have to choose how to view your blog - if you choose to offer the mobile template.

>> Top

After Using "Buy a domain", Blog Owners Are Seeing "Server error" From Google Apps

Ever since Google ended its free Google Apps accounts, we've been seeing reports in Blogger Help Forum: Something Is Broken, about problems encountered when setting up a new Google Apps account, to administer a newly purchased custom domain.

Every time I try to login to Google Apps, using instructions in the email message, I get

Server Error: We could not process your request at this time, please try again later.

The limited function free Google Apps accounts, which can be only used for domain maintenance, do not work with the Google Apps account setup wizard, which is generally used after using "Buy a domain". When you see "Invalid request" or "Server error", you need to reset the password for the "bloggeradmin" account, for your domain.

Start by accessing the Google Apps administrative account reset wizard, for your domain. If you use GMail for your email, or other Google products, try to use a different browser for Google Apps. Alternately, use an "Incognito" window, in Chrome - or a "Private" window, in Firefox. Or, clear cache, cookies, and sessions - then restart the browser, when possible.

For this domain, "nitecruzr.net", I would access the account reset wizard as

http://google.com/a/cpanel/nitecruzr.net/ResetAdminPassword

or possibly

http://google.com/a/nitecruzr.net/ResetAdminPassword

You simply change "nitecruzr.net", to your domain URL, to reset the administrative password for your domain.

---

(Update 2013/11/03): This process should be slightly simplified, with Google Apps now using the new integrated Google login screen.

---

Having solved the CAPTCHA in the reset screen, Google will send a password reset email message, for the "bloggeradmin" account for your domain, to the email address used by your Blogger account. Once again, this is a bad time to be using Blogger anonymously.

Open your email, then open and execute the email message, to reset the bloggeradmin Google Apps account. Be sure to enter the complete Google Apps account name, in the Google account reset screen.

Once the password is reset, login to Google Apps. Then retrieve the login tokens, from the Google Apps desktop, to access eNom or GoDaddy.

>> Top

Use Free Online Website Display Services, To Diagnose Browser Related Problems

Look at the Audience display, in Stats. How many different entries do you see, in "Pageviews by Browser" and "Pageviews by Operating System"? Stats lists are limited to 10 entries, each. Do you ever wonder if those lists, like the other Stats lists, should be longer? How do we ever hope to observe our blogs, and see what they look like, for our many different readers?

One of the challenges of publishing a Blogger blog is developing a blog that looks good, on every reader's browser and computer. The number of combinations of operating system times browser brand times browser version - any of which can create a display oddity, when viewing any blog or website - is staggering.

How can we ever hope to produce a blog that's universally readable? We can always (depending upon the capacity of the computer(s) which we may use) use different browsers, to monitor ongoing issues which might affect our blog's legibility. Knowing the real number of combinations that may affect our readers, will using one or two alternate browsers (on one single operating system) really accomplish much?

One way that we can keep some running idea what our blogs look like, in different browsers, is to use an online browser display analysis service. This is an essential part of verifying proper formatting, as we make changes.

Free online services, like AnyBrowser or BrowserShots, will show you what your blog looks like, by simulating it on different browsers. Their displays, on your browser and your computer are obviously subject to peculiarities of your browser and computer, of course - but their services are a good start.

For in depth research, the W3Schools Online Web Tutorials will identify, in detail, which features are supported, in different browsers.

>> Top

Stats And The "Don't track your own pageviews" Option On Mobile Computers

As mobile computing becomes more popular, we're starting to see questions about use of the Blogger dashboard on mobile computers (iPhone / iPod, PDA, smart phone), in Blogger Help Forum: Something Is Broken. Most recently, we're seeing people trying to use Stats, and the "Don't track my own pageviews" option, with Blogger on mobile computers.

Problems with Stats and the "Don't track ..." option are not unknown, in the past. We've helped many blog owners with this setting, which is sensitive to cookie and script filtering in general - and to "third party cookies" in particular. "Third party cookies" may be filtered in any of several places, any which will interfere with "Don't track ...".

The "Don't track ..." option, when seen as a problem with "full size" computers (desktop, laptop / notebook), may involve any of various "layered security" settings. In general "full size" computers use a somewhat standard software infrastructure. While any of several operating systems (Apple / Macintosh, Chrome, Linux, Microsoft Windows), and various browsers (Chrome, Firefox, Internet Explorer, Opera, Safari) make use of Blogger an occasional challenge on "full size" computers, there is some common features between the various operating systems and browsers.

With the various "operating systems" and browsers on mobile computers, we're seeing more discrepancies in features offered. In particular, not all "mobile computers" have explicit settings to allow / disallow "third party cookies" - or even cookies and scripts, in general. If these settings are not present, it's likely that these computers do not support such details as "third party cookies".

Without the availability of "third party cookies", Blogger can't support the "Don't track ..." option. Here, I'll note that this option is specific to each individual browser, on each individual computer. One must set the option - and browse the specific Blogger blog - using the same browser, for the option to work. This is not an option that can be set on a per user basis, and apply to all browsers used by a specific user.

>> Top

Blogger Magic - Verifying A Blog Feed URL

It's a fairly simple matter to determine the newsfeed URL, for any given blog, by examining the blog template code.

Besides the base feed, a blog may publish an extensive array of additional feeds, which won't be listed directly in the blog template code. You may use any given feed, in networking your blog, with any Google or non Google service.

Starting with any feed URL, what do I do? I could just open my favourite feed reader, or social networking web site, and paste the URL in place. But what if the feed reader or web site wasn't working properly, or I misunderstood the instructions? What if I see

Invalid URL

or the like, what do I do?

The smart thing to do, before you setup a FeedBurner feed or any complementary non Blogger service, is to test the feed.

Many modern browsers (Firefox or Internet Explorer, for instance) will give you a formatted display, when you are loading a feed URL.

Use A Well Protected Browser, To Block Redirecting From Misbehaving Code And Gadgets

Regularly, in Blogger Help Forum: Something Is Broken, we advise people about problem code or gadgets in their blogs.

Generally, this follows reports by blog owners, that their readers are being redirected to unexpected and unwanted blogs and websites, from their blogs. Sometimes, we get the reply

I can't remove the code. Every time I login to Blogger, I am redirected, just as my readers are being treated!

When we see the latter complaint, we recognise yet one more blog owner who does not know how to properly protect himself, from malicious code and websites. Most people, who know about Layered Security, know that proper browser security is an essential complement to a properly chosen and maintained anti malware filter.

Many people, who care about browser based security, use Firefox with NoScript.

This combination provides Unix level security, "deny by default, permit by exception". Simply install NoScript as an add-on, to Firefox, to get started. Alternately, you may use Chrome with ScriptSafe, or Opera with NotScripts.

When using your browser with a script filter, there will be specific Blogger / Google websites which you should trust, and others which you should not trust.

Every time you surf to a different website - and decide that the owners of the website, which you are now viewing, have your best interests in mind - configure NoScript to allow that website, to display properly on your computer. When you find that a trusted host website does not display properly, examine the NoScript taskbar and the list of websites used by the host website. Look at the NoScript Options menu, carefully. Allow specific websites which you trust, and Forbid all other websites which you do not trust.

Deciding which websites to trust, based on their presence in the NoScript Options menu, will be a learning experience for a while. For some host website pages, which use a large number of unfamiliar websites, you may have to carefully select to "Temporarily allow all this page" - or you can "Temporarily allow" each single website, one by one, until the host website page displays properly.

When you decide to (permanently) "Allow" any website, that website will be "Allowed" on all other host websites where you may surf. Conversely, any website which you never select to "Allow" - such as the problem website which is providing the misbehaving code - will never execute on your computer again. This will prevent redirection on your computer, allow you to safely use the Blogger dashboard, and edit or remove any dodgy code which may be part of your blog.

After removing any dodgy code from your blog, always clear cache and restart Firefox, to test the effects of your editing.

>> Top

Blogger Blogs Lack The Navbar, Though Not Removed By The Owner

Recently, a few Blogger blog owners are looking at their blogs and wondering

Where is my Navbar?

or

Why don't I have a "Sign In" ("Sign Out") link, at the top of the page?

When investigating further, they may discover that none of the blogs, that they view, shows the Navbar. And, they did not intentionally make any template changes, to their blog, to hide the navbar.

Many of these people, later investigating the problem in Blogger Help, learn that their browser, or another anti malware product, is blocking the navbar as suspicious code. This is another example of improperly configured layered security, planned to protect our computers.

If you are observing the lack of the navbar on your computer, and you request help in Blogger Help, please help us to help you better, and provide details.

• What browser (name and version - and precision matters) are you using?
• What add-ons are installed, in the browser (completeness matters)?
• What anti malware product(s) do you use, on your computer (again, completeness matters)?

If we can get an idea of what components are involved in this problem, maybe we can isolate the problem, itself. Please, be complete - and be precise.

>> Top

Blog Owners Reporting The New Blogger GUI Display Is Garbled

We have recently seen a few reports in Blogger Help Forum: Something Is Broken, concerning the New GUI display, which is broken for some blog owners.

When I login to Blogger, the interface doesn't display properly. Everything is shifted and some buttons appear to be missing.

The reporting volume, mentioning this symptom, is low - but it's not random, or zero.

From what we can tell, this problem started shortly after the latest Microsoft Windows updates, a week ago. Microsoft Answers: Computer Display Messed up After Restart discusses this problem, and essentially suggests that you should download video drivers from the vendor of the video device in your computer - and to not depend upon Microsoft, to provide you updated third party drivers.

If you are unable to use the Blogger Interface because the display is unreadable, with components missing or mislocated, you're going to have to update the video drivers on your computer, using drivers obtained from the manufacturer - not from Microsoft. This is not a problem caused by Blogger.

If the browser involved in the problem is Internet Explorer, you also may need to check your Compatibility View setting.

>> Top

Internet Explorer V8 / V9 And The New Blogger GUI

Back when Internet Explorer V8 was first released by Microsoft, and Blogger had yet to update their code to allow for its peccadilloes, some Blogger blog owners used the Internet Explorer "Compatibility View" switch, to make their browsers work with Blogger (when they were using the Blogger "Classic" GUI).

We've recently been seeing an increasing number of people in Blogger Help Forum: Something Is Broken, using Internet Explorer, who report problems with The New GUI.

With Blogger code written for Internet Explorer V8 / V9, people who use Internet Explorer V7 - or use V8 / V9 that runs as if V7 (with "Compatibility View" enabled) - are having problems using the New Blogger GUI.

The most popularly recommended solution for problems like the White Screen Of Death has been to switch back to the Classic GUI. A more effective long term solution, for people using Internet Explorer in Compatibility Mode, would be to stop using Compatibility Mode.

1. From the Internet Explorer menu, select "Tools" - "Compatibility View Settings".
2. In Internet Explorer, click on the "broken page" icon, at the end of the address bar.
3. Remove "blogger.com" from the "Compatibility View Settings" list.

Don't have Internet Explorer work like IE V7, now that Blogger has updated their code - and IE V7 is not supported.

>> Top