Powered by Blogger.
Menu :
Showing posts with label Blogger Mystery. Show all posts
Showing posts with label Blogger Mystery. Show all posts

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

Problems Adding / Editing The HTML And Text Gadgets

We're seeing a few reports, in Blogger Help Forum: Something Is Broken, mentioning problems adding or updating the HTML and Text gadgets. The most common symptom is very simple.
When I try to update the gadget, all that I see is
javascript:void(0);
In this case, we have to first explain that "javascript:void(0);" is not the problem - it's simply a symptom of the problem.

Once we explore the problem itself, we see various possible causes.

The base cause for problems with the HTML / Text gadget is simple - the script which processes gadget updates provides no diagnostics when detecting errors.

If you were to update a post, or the template, with bad HTML, you'd see some error message, indicating that your changes are bad.

Both Post Editor and Template Editor provide some diagnostics, when errors are detected. With the HTML / Text Gadget, the script issues no error messages, it simply stops.

Instead of "javascript:void(0);" displaying for a fraction of a second, as the update is saved and the window closes, the blog owner is left looking at
javascript:void(0);
until he hits "Cancel" in confusion.

The HTML / Text gadget has been observed to have various problems, which prevent changes from being properly saved.
  • Bad HTML, when accidentally in HTML mode.
  • HTML / JavaScript code which contains line breaks in the wrong places.
  • Bad HTML code, when intentionally entering an HTML gadget.
  • Gadgets with blank titles.
  • Layered security, which blocks the gadget update scripts from running.
  • Trying to use a non supported browser version.


Blog owners who are not observant, when updating the gadget, may accidentally be in HTML mode. Rich text, containing HTML significant characters, will be a problem.

HTML / JavaScript code is sensitive to line breaks in the wrong places in the code. Blog owners, accidentally or intentionally inserting line breaks, can cause a problem.

HTML / JavaScript code, in general, is syntax sensitive. Bad code will always be a problem.

Gadgets with blank titles will cause a problem, when using some browsers. If a gadget with a blank title is specifically required, it may be possible to use a null title, instead.
<!-- -->

Inappropriate use of layered security may block cookies or scripts, and prevent the gadget from updating.

The gadget, like every other Blogger feature, must be updated to support newer browser versions. It will likewise be updated periodically, to remove support for older browser versions. Non supported browser versions will frequently cause problems.

Some of these error scenarios should be more clearly identified, by the script - but not all can be identified. Attempting to save a gadget with a blank title, for instance, should produce a stern warning
Blank titles are not accepted.
Unfortunately, HTML syntax errors generally can't be consistently diagnosed, with any detail.

The best solution here is for the blog owners to be aware that the gadget operates this way, when being updated. Some cautious effort must be made, when updating the gadget.

It's possible that problems updating the gadget, like many Blogger problems in general, can be best diagnosed using affinity testing, and / or differential testing.

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