bollywood latest news

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

We see occasional signs of naivete, in Blogger Help Forum: How Do I?, about custom domain publishing.

Can I publish to a custom domain - and still use the Blogger dashboard?

and

Can I publish to a custom domain - and keep my comments and posts?

and

Can I publish to a custom domain - and avoid TOS restrictions?

Some blog owners seem to see custom domain publishing as more than it actually is.

When you publish your blog to a non BlogSpot URL (aka custom domain), using a proper setup, your blog now has a new URL.

The BlogSpot URL continues to work - and to direct search engines bots, search query results, and visitors, to the blog.

If your blog uses Google+ Comments, you won't see the comments published to the BlogSpot URL - although the comments will still exist, and be visible, in Google+.

Some accessory gadgets will stop working, temporarily, shortly after the new URL starts working. This is an unavoidable result of the Internet address lookup infrastructure, aka DNS.

Other than those details, you'll have the same blog as before - just with an extra URL, that may be more valuable to the search engines.

• The Blogger blog will still be hosted by Blogger / Google, and will use the Blogger dashboard for maintenance and publishing.
• The blog will be served subject to Auto Pagination.
• The blog will be subject to the same content restrictions - both porn labeling, and malware / spam deletion, will be consequences of any infractions.
• The blog will be subject to the same deletion recovery restrictions.

Just as any time you change the URL of your blog, you'll face changes in external relationships, such as with your readers, and with search engines and other services. Don't do this without careful planning, and methodical execution!

For the few times when your domain fails, see my troubleshooting check list - but prevent problems best, by first setting it up properly, and by observing your own limitations.

>> Top

In some cases, the earlier provided procedure, for accessing the limited access domain administrator account, may not work, for your Google Apps domain.

For some Google Apps domains, you will need to reset the password using the Google administrative reset. Instead of the wizard at "accounts.google.com", you may need the administrative reset wizard, at "https://admin.google.com".

A Google Apps administrative account reset uses the same set of displays, as the previously discussed limited access account reset.

When you request administrative account reset, you first try the using default account name.

For my domain, if it had been purchased after November 2012, the default account name would be "bloggeradmin@nitecruzr.net". Yours will be "bloggeradmin@yourdomainURL" - whatever "yourdomainURL" actually is.

Domains purchased before December 2012 will apparently still use a Google Apps token sent in email or linked from Google Wallet.

As previously advised, always use one browser for Blogger and other Google activity like GMail, and the second for the Google Apps session. For best results, first clear cache, cookies and sessions (yes, all 3!), and restart the second browser.

Use the same account name, as advised - just substitute the administrative reset sequence.

https://admin.google.com/

Click on "Need help?".

Select "I don't know my password".

Enter your limited access Google Apps account name.
In most cases, you will go into the expected administrative account reset sequence.

With a mature account, where you have previously setup a custom administrative account, "bloggeradmin@yourdomainURL" may not be accepted. Now, you must try an extended administrative account reset.


If the limited access account, for your domain, is not operational, don't panic.

Return to the previous screen, and select "I don't know my username".

Now, you have other details to provide.


Whether you use the standard administrative reset - or the extended administrative reset - Google will send a password reset email message, to the backup email account associated with the domain. The email account should be the one used by the Blogger account, under which you purchased the domain.

Other than the previously enumerated cases where you can't use the recovery email address, this should be a reasonably straightforward process.

1. Access the new Google Administrator Login screen.
2. Click on "Need help?".
3. Request password reset.
4. Access the right email account.
5. Open, and execute the password reset email.
6. Hopefully, you're done.
7. If necessary, return to the previous screen.
8. Select "I don't know my username".
9. Provide additional details.
10. Go to Step 3.

Once you're in the Admin Console, you can check / set the auto renewal option setting, or you can retrieve the login instructions to access the registrar's zone editor - or do whatever else you need to do.

The next time you need to access the Admin Console, try to remember the previously set account name and password. And, if you feel up to it, add recovery options to your administrator account.

>> Top