Your Google Apps Account, And The New Administrative Google Login

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

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

Your Google Apps Account, And The New Google Login

In the not so distant past, explaining how to login to Google Apps was a painfully tedious process.

If I wanted to login to the Google Apps account for this domain, "nitecruzr.net", I would construct a URL in the browser address window (or use a bookmark)

https://www.google.com/a/nitecruzr.net/ServiceLogin

The URL for your domain would be different - and explaining the difference was frequently a nuisance, in the login sequence instructions.

When explaining how to login to a recently created limited access Apps account, I would focus on the account reset process.

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

Again, your URLs would differ. Maintaining separate bookmarks, for each different domain, was a time sink.

With the new Google Apps integrated account login, all of that has changed.

Any time you start a process which involves Google accounts, first clear cache, cookies and sessions (yes, all 3!), and restart the browser.

Since the Google Apps login uses a different Google account, you'll need to use two browsers - as you do when transferring control of your blog.

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.

Next, to login to the limited access Google Apps account for this domain, you simply go to the standard Google login screen, using the second browser.

https://accounts.google.com/ServiceLogin

You then click on "Need help?". On the next screen, select "I don't know my password", and enter the limited access Google Apps account name, for your domain.

For my domain, if it had been purchased after November 2012, the default account name would be the limited access "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.

Enter the appropriate account name, click "Continue", and follow instructions.


Click on "Need help?".

Select "I don't know my password".

Enter your limited access Google Apps account name.
After you submit the password reset request, Google will send a password reset email message, to the backup email account associated with the domain. The email account, for a new Apps account, should be the email account used by the Blogger account, under which you purchased the domain.

The only problem which you can have is if the necessary email account can't be accessed.

• Being overly secretive, and basing the Blogger account on a bogus or inactive email address.
• Having the Blogger / Google account deleted for abusive practice.
• Never bothering to remember the email account and password.

In either case, without access to the right email account, you won't be able to reset the Google Apps account password - and you won't be able to gain / regain access to your Google Apps domain administrator account, aka the "Admin Console", for the domain in question.

Other than that one possible problem, it should be a straightforward process.

1. Access the new Google 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.

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.

If you're logging into Apps for a second time, and you remember the account name and password, it's simpler still. Access the new Google Login screen, enter the domain administrator account name and password, and login. Now, Google Apps is just one more Google application - but with its own unique account name.


If you remember the domain admin account name and password from last time, just login - and you're there.

Again, always open Google Apps in a second browser.

Other than the need to use a second browser, logging into Google Apps is now a series of bookmarks and simple scripts.

---

In some cases, you may not be able to use the limited account reset sequence. Don't panic! Google also provides an administrative account reset process, for these situations!

---

>> Top

Export / Import Requires Administrative Control Of Both Blogs

Occasionally, in Blogger Help Forum: How Do I?, we see the naive query

How do I merge my two blogs, using Export / Import?

When given the simple advice

Use the "Export blog" and "Import blog" wizards, both in the dashboard Settings - Other menu.

the immediate response is

I don't have that menu item!

This person has, most likely, lost control of the Blogger account.

In order to avoid encouraging scraping of blog contents, both the Export and Import wizards are only available to blog administrators. Not everybody wishing to use "Export blog" has blog ownership, however.

Too many people, denied immediate recovery of control of their blog, just start another blog.

With a new blog, the first thing needed is the content from the old blog. This is not easily had, however - because both "Export blog" and "Import blog" are part of the Blogger dashboard - and can be accessed only by blog owners.

If anybody could use "Export blog", and export the comments and posts from any blog, "Export blog" would be a very popular wizard - to blog thieves. To encourage Export / Import to be used for legitimate purposes, Blogger made it part of the Blogger dashboard - where it is accessible only to blog administrators.

This does not provide a solution for people who have lost control of their Blogger accounts - and who naively figure to start a new blog, and move the contents of the old blog to the new blog. If you're in this situation, you have only two possibilities.

1. Recover comments and posts using blog feeds and online cache.
2. Cluster the new and old blogs - but asymmetrically.

You can link from the new blog back to the old blog, using any combination of imaginative techniques - but without control of the old Blogger account, you're simply not going to be able to link from the old blog to the new blog.

Sorry. Once again, you have to always retain control of your Blogger account.

>> Top

Being A Hacking Victim Is Not Always The Fault Of The Account / Blog Owner

Even though being the victim of a hacking attack is not (always) the fault of the account / blog owner, the blog owner may have to bear some of the responsibility.

Since hacking detection is a fuzzy process, it's not always going to be detected immediately. The previous article discusses what happens when Google does detect a hacking attack - and in some cases reacts too diligently.

If Google is not able to detect an attack, in some cases, an attack may be successful.

With some blogs, that are not updated frequently, a hacker may take control, and successfully hijack a blog.

Occasionally we see another report

I just discovered that my blog contains spam - and I can't access the dashboard, to clean the blog!

This may well be a successfully hijacked blog, discovered too late.

Unfortunately, the latter report may also be another devious attempt to steal control of somebody's blog. Blogger Support cannot, reliably, support hacking recovery, on an individual basis.

From what I can tell, Blogger / Google is working on the larger picture - making the automated detection process more reliable. Given this concern, Blogger / Google won't be frequently available to diagnose and return control of individual hijacked blogs - even when the issue is righteous.

In general, blog owners have to support themselves, and learn how to protect themselves. This may be yet one more reason why 2-Step Verification is becoming less optional.

>> Top

Recovering Stolen Blogs Is Not An Open And Shut Case

Recently, we've seen a few problems reports, in Blogger Help Forum: Something Is Broken, requesting return of blogs stolen from the rightful owner.

Supposedly, the "rightful" owner is the person posting the problem report. We've learned from past experiences that this may not always be the case, however.

Long ago, when a stolen blog claim was posted in the forum, we could report it to Blogger Support as a "blog theft".

In many cases, given enough patience, Blogger Engineering and Google Legal would carefully examine the blog ownership history, and eventually restore the blog to its "rightful" owner. Unfortunately, even with the most careful forensic examination, the "blog theft" claim was occasionally used by hackers, to steal other peoples blogs.

Most recently, when "blog theft" is reported, Blogger Support declines to consider the case. Considering all of the issues, we generally see that they are making a responsible business decision.

Instead of spending massive amounts of time verifying individual claims, Blogger Engineering appears to be working on overall improvements to Blogger - to encourage blog owners to not put themselves, or their accounts and blogs, in unrecoverable positions.

Any blog which contains abusive material - whether malware, porn, or spam, or illegally obtained material - can be reported using the proper complaint form. Blogs which do not contain abusive material are the property of the current owner - and Blogger / Google will respect and support the current owner.

Blog owners, claiming theft, can generally report a stolen blog as abusive - if the current content justifies that claim. Other than that, the best solution is to hire a lawyer and convince a judge to issue a court order - and require Google Legal to become involved.

The issue of Blogger account and blog recovery is a long and painful one - for many people.

>> Top

Anonymous Blog Ownership, And Hacked Account Detection

This week, we're seeing a number of reports from blog owners with Blogger accounts recently hacked.

I was asked to change my password, because of suspicious activity. Having done that, my blogs are now deleted!

With hacked Blogger / Google accounts, causing deleted blogs, there's not a lot of advice that we can provide.

As you just discovered, the account is recovered almost immediately. Blog recovery, unfortunately, takes longer - sometimes, 1 to 2 days. You'll have to wait, patiently, until your blogs are verified by Google Security staff.

We're also seeing the normal amount of reports of blogs deleted by Blogger, when detected for malware, porn, or spam. In some cases, blog review ends with the conclusion that the blog was not, in fact, deleted for a TOS violation. In these cases, the blog won't be restored by Blogger Support.

In some cases, blog review - which starts with a claim of spurious classification for malware, porn, or spam hosting - ends with advice to have the owning Blogger / Google account recovered.

The blog owner has to wait until the review process is complete, to learn where he should have started, days ago. As I've observed a few times in the past, anonymity - whether intention or accidental - can cause problems with blog ownership. If your Blogger / Google account is locked, but you don't get the required notification, you can waste valuable time with the blog offline.

Whether you intentionally anonymise yourself - or accidentally create a second (or third) Blogger account, you may not get essential email from Google, advising you to recover your account. When that happens, your blog will stay offline until it can be reviewed - and review starts only after you recover the account that was locked.

Now, you're going to have to open every possible email account, and carefully look for the overlooked email. If you never find the missing email message, you're going to have to login to Blogger, using every possible email address that you may have ever used, until you hit the locked Blogger account.

When you do identify the locked account, you'll get the advice to change your password, solve a CAPTCHA, and / or answer a number of secret questions, to prove that you are the account owner. Or, if you're lucky, you can await a phone call (digital or voice) with a special code, to unlock your account. Either way, you'll be unlocking the account while under stress, with the blog offline.

And after you get the account unlocked, you'll still have to wait until the blog(s) can be verified.

If you try to blame Google, for this disaster

Why was my blog deleted? I did not spam!

you will simply be wasting your time. This is yet one more story that starts with gratuitous and uncontrolled creation of multiple Blogger accounts and email addresses.

>> Top

Use Google 2-Step Verification, To Protect Your Blogger / Google Account - And Your Blogs

Our Blogger accounts, and blogs, are under persistent attack by some rather nasty Internet users.

Hackers, using other peoples computers, are constantly attempting to "guess" our Blogger passwords, and take control of our Blogger accounts and blogs. Blogger accounts are particularly vulnerable to attack, because too many blog owners

• Reveal their account names (email addresses) to the world.
• Base their passwords upon real life details.
• Publish blogs, where their real life details are visible to the world.

Some blog owners think that by using only one computer forever, they should be able to register that one computer as theirs, and require Google to simply deny access to their Blogger / Google accounts, from any other computer. This is a very simple solution - and it's one which is doomed to failure.

Google knows that even the most careful person will periodically use a different computer - or possibly forget their Blogger account name and / or password.

Rather than attempt to restrict us to using one single computer, for eternity, Google gives us an option to use a previously registered telephone as an authentication token, whenever we use a different computer. The telephone can use either text or voice, and provide us with a one use passcode, to enter after we successfully enter our account name and password.

This is not a foolproof solution.

• Some people will not want to provide their phone number, to Google.
• This strategy will only work with a preregistered phone - and registration can only be done when we are logged in to Google.
• If the pre registered phone uses text (a smart phone / mobile computer), it will be usable only where cellular service is available.
• If the pre registered phone uses voice, it will be usable only as well as we understand computer synthesised "speech".
• In either case, in some cases, stress will contribute to the possibility of making a mistake.
• Since a pre registered phone is required, we will be able to use this only as long as we carry our smart phone - or login from a pre determined location.

However, if we can deal with the above drawbacks, we have a much better chance of keeping our Blogger accounts and blogs under our control. Very few hackers, having successfully provided our account name and password, will be able to immediately use a pre registered telephone, to accept a one time use passcode.

>> Top

The Google Apps "bloggeradmin" Password Reset May Be Broken, For Some Domains

We've been seeing reports from some frustrated blog owners, about problems with the limited access Google Apps accounts.

I've reset my password numerous times and it still doesn't work.

Even given the recently provided "bloggeradmin" username, and the standard Google account reset process, some blog owners still cannot access Google Apps to manage their Blogger custom domain published blogs.

We do have one bit of hope. One such problem report, recently forwarded to Google Apps Support, was noted by a Google Apps Engineer with the advice

We identified a recent change which may have affected the password reset flow for some users. We expect it to either be fixed or rolled out shortly.

So, there is some hope for a few unhappy new domain owners. It's possible that this problem has been resolved, with Google Apps now using the new comprehensive Google login screen.

>> Top

The Google Apps "bloggeradmin" Password Reset Uses A Standard Google Account Reset

As Google Apps updates their limited function ("bloggeradmin") account setup process, we see reports from confused Blogger blog owners.

After I reset my password, I still get

The username or password you entered is incorrect

when I try to login, later!

and

I reset my password - and it changed my Blogger and GMail account - but I still can't login to Google Apps!!

The Google Apps password reset uses a standard Google account reset process - and is subject to normal account reset behaviour. If you don't reset the right account, you won't be able to login, later.

We've been warning people for years, about the need to use two browsers, to transfer a Blogger blog from one Google (GMail) account to another.

The Google Apps "bloggeradmin" account setup, like the Blogger blog transfer, works best using two browsers. The password reset, for "bloggeradmin@mydomain.com" (as an example, here) involves a Google account reset.

1. You start the password reset from a Google Apps login screen, for "mydomain.com".
2. After clicking on the "Can't access your account?" link, you use a standard Google account reset process.

When you attempt to login to Google Apps, click on "Can't access your account?". That takes you into the Google Account Reset process.


Provide the full account name of your Apps account.

bloggeradmin@mydomain.com

instead of

myemail@gmail.com

The Google Apps password reset, like blog account transfer, is one more process where you may need to use two different browsers. And, to be safe, clear cache, cookies, and sessions (yes, all 3!) - then restart the second browser, before opening the password reset email.

The password reset will be more likely to be successful, if your Blogger account is based on an active and real email address - this is not a good time to be anonymous.

---

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

---

>> Top

Recovering And Protecting Your GMail Account

Blogger blog owners may have productive action, when their Blogger accounts are successfully hacked through an attack on their GMail accounts.

GMail account owners can get detailed instructions on recovering a successfully hacked account, and on preventing future hacking attacks from being successful. Some of the instructions are specific to GMail use - but overall, Blogger account owners will benefit from their use.

To benefit from the GMail instructions, one should consider the differences between Blogger, email, and Google accounts.

Gmail Account Recovery: Gmail Account Recovery and Security provides complete and detailed instructions for recovering a hacked and stolen GMail email account.

The Recovery instructions include specific mentions of Disabled / Suspended accounts, successfully Stolen accounts, and accounts locked or deleted because of Underage owners.

Accompanying the recovery advice is Gmail help and information: How NOT To Get Hacked. These are instructions for preventing a recurrence of a reported problem. This includes discussion of using a strong and secure password, identifying hacking techniques that involve the account owner, and preventing attacks which are conducted using the computer or network in use by the account owner.

The Prevention instructions, many which are common sense issues to any IT professional or security expert, are specifically written to apply to GMail account owners. There may be additional issues which apply in general, to Blogger accounts - and specifically, to Blogger accounts which are based on non GMail email accounts.

There are a few differences between Blogger blog ownership and GMail account ownership, which will cause issues that cannot be easily resolved by Blogger Support, or by GMail Support, to the satisfaction of the (former) blog owner.

GMail accounts are, by nature, single owner - and ownership of a GMail account is never transferred. In contrast, Blogger blogs can be under team ownership - and ownership can be transferred.

• Intentional team blog ownership. Team blog ownership can cause problems with loss of blog control, when all known blog administrators (accidentally or intentionally) remove themselves as administrators, leaving an unknown administrator.
• Intentional transfer of control. A blog owner may assign administrator status to another person, voluntarily - then later regret his decision.
• Un intentional transfer of control. A blog owner may assign administrator status to another person, voluntarily - and the other person may then remove the former owner administrator status.
• Ownership theft after account hacking. A hacker, having temporarily gained control of a Blogger account, may transfer ownership of a blog to another Blogger account.

All of these scenarios are regarded as simple transfer of blog ownership, by Blogger Support.

Though maybe not preferred by the (former) blog owner, the blog in question will now be under control of another person. It's possible that some of these scenarios are considered by Google Security, when reviewing Blogger / Google accounts after hacking activity is detected.

Blogger accounts, based on non GMail email addresses, will be subject to the typical uncertainty which accompanies any third party service in Blogger. Some details may be involve the email provider, while others will involve Blogger - and arbitrating between the two will be the responsibility of the Blogger account owner.

Owners of Blogger accounts which are based on non GMail email addresses will need to contact the providers of the actual email service, for resolution of some of these issues.

In general though, the GMail Account Loss Prevention and Recovery instructions provide good advice, for any Blogger account owner.

>> Top

If You Cannot Prove Ownership Of Your Blogger Account, Your Next Step May Involve Court Action

We've explored the issues of Blogger account and blog recovery policy, repeatedly. We've mentioned the business concerns, the personal support issues, and even the strategic hacking possibilities. Even so, we continue to see evidence of blog owners who just don't understand the message, posting in Blogger Help Forum: Something Is Broken.

I started a blog under an alias, to be able to post anonymously, and can't remember the login details or the e-mail recovery. How can I regain access to my blog?

Last year, Blogger Support offered the "final" word about account recovery assistance, in the forum.

Due to the sensitive nature of these issues, we won't be able to troubleshoot your issue in this public forum.

Even giving that advice, some blog owners still insist that Google is not cooperating, in refusing to restore access to Blogger accounts and blogs, to people who cannot prove their right to ownership.

The policy on ownership recovery is quite simple. Anybody requiring recovery has to prove their right to a given Blogger account or blog, using the tools provided.

Because Google doesn't ask for much personal information when you sign up for an account, we don't have many ways to verify that you own an account.

Blogger / Google provide two automated recovery tools - and that is the limit of their cooperation. Every Blogger blog owner, who actively publishes a blog, and who wants to keep their blog under their control, needs to appreciate this limit - this is how Blogger and Google prevents devious hijacking of our blogs.

For those blog owners who truly need - and deserve - control of their lost blogs, there is one final recourse. Any owner, who cannot use the Blogger / Google automated tools, are entitled to take their concerns outside Google, and have their identity certified by the courts. Start by hiring a lawyer, take the matter to a judge, and get a properly issued court order. Then, serve the court order, properly, to Google.

Let's let the courts assume responsibility of deciding who is a worthy blog owner - and who is potentially a hacker.

>> Top

Blog Readers Report Comments, Supposedly Published Using A Mobile Computer, Appear To Disappear

Recently, we've been seeing a few problem reports in Blogger Help Forum: Something Is Broken, mentioning mobile computers and problems publishing comments on Blogger blogs.

My readers tell me that they can't comment on my blog, using an iPad. Comments disappear, when they try to publish them.

As with a previously explored problem with comments on a non mobile computer, this problem may involve unfamiliarity with the publishing sequence.

The dialogue involved in publishing a comment, when using a desktop computer with a full size display and a non mobile Blogger template, is not simple. Depending upon the various commenting options selected by the owner, the publishing sequence may be even more complex. Blog owners may need to consider the additional details involved in comment publishing, when using a mobile computer.

Using Blogger on a mobile computer involves various compromises - and the comment publishing process on a mobile computer even more compromises.

• The small display size, on a mobile computer, makes finding the various controls involved a challenge. Both the small size of everything involved, and the necessity of repeatedly scrolling around the screen, looking for the controls used in comment publishing, is frustrating.
• The "mobile template" is an attempt to make up for the small display size. The mobile template puts the various controls on a series of displays, with various buttons and links used to move from display to display.

People unaccustomed to the sequence of steps involved in the comment publishing process may not see all of the controls required, when using a mobile computer. Neither the wide non mobile template, nor the deep mobile template, displays the comment publishing sequence easily. People who are not very experienced with the comment publishing process, in general, might become confused with the displays.

As an example, let's look at the basic comment entry dialogue. So simple - when you are used to it, and can see all of the components.

• On a desktop / full function display, you'll see an entry box, and a "Publish" button beneath the box. You use the keyboard and / or mouse to enter text into the box, then click on the "Publish" button.
• When the required display space is larger than the physical screen space, you'll have a horizontal and / or vertical scroll bar, indicating that scrolling is required, to locate other display content. You'll use the mouse to manipulate the scroll bars, and make other portions of the display visible.
• A mobile display will have an entry box, and an on screen keyboard. The onscreen keyboard will occupy a fixed amount of display space, with the entry box occupying the available remainder.
• The mobile display won't have scroll bars - if other portions of the display are not immediately visible, you'll use your finger to scroll around the screen. If you are not familiar with screen layout, you'll have to scroll around, aimlessly.
• The "Publish" button will be somewhere near the entry box - but depending upon screen size and orientation, may not be immediately visible. You may have to scroll around the screen to find the "Publish" button.
• People not used to using a mobile computer may be unable to find the "Publish" button. Finding other display content that may appear to replace the "Publish" button, they may be confused when their comments are not published, and report that their comments disappeared.

Both the authentication sequence (when authentication is required), and the CAPTCHA entry sequence (when a CAPTCHA is involved), when involved in mobile computing commenting, will make the comment publishing process even more complicated. The authentication sequence may be more complex, if the browser in use has a problem with Blogger authentication - and "third party" cookies.

Since most blogs are designed primarily for non mobile computer use, commenting using mobile computers may not be obvious, for a while. Many readers may simply not publish comments, to the same activity level, when using their mobile computers.

>> Top

Enabling Blogger, If You Now Have An ISP Provided Email Account, That Uses Google Apps Based GMail

We're seeing problem reports from some confused blog owners, who are apparently customers of ISPs who have made the switch, from using a private email infrastructure, to using GMail based email (administered using Google Apps).

When I try to sign in I get this message.

Blogger has not been enabled by the administrator of the domain

How do I administer my blog?

We've known, for a while, that having a Blogger account based on a Google Apps provided GMail account may not be a good long term strategy - particularly if the Apps account is based on a domain which you own, and the domain was purchased to host one of your blogs.

Possibly considering the latter scenario, Blogger / Google now requires that you enable the Blogger service, for any new Google Apps controlled domain - if you wish to use email addresses in that domain to host Blogger accounts. This is a safety measure, helping to prevent you from having a Blogger account that you can't control - or can't recover access when you forget the password.

All of that is fine - when you control the domain that you wish to use to host your Blogger account. But what if you don't control the domain? What if you previously setup a Blogger account based on your ISP's email domain - then later the domain administrator decides to upgrade the domain, to use GMail based email? What happens to your Blogger account?

Short of convincing the domain administrators for your ISP that you have a genuine and urgent need to have a Blogger account, based on an email address that they provide, you're going to need a new email address - provided by someone other than Google, or your ISP (school, employer, what have you).

Start by setting up an email account in some third party web service - maybe "Yahoo.com". Then, you have two possibilities. If you're reading this article just before your ISP makes the switch, and you can still use your Blogger account, transfer control of your blog(s) to a new Blogger account that's based on your new email address.

If you just discovered the change by your ISP - maybe because you now see the bad news

Blogger has not been enabled by the administrator of the domain

you are going to have to recover control of your blog, based upon access to your ISP's email account - and setup a new Blogger account based on your new non ISP based email account.

1. Generate a new account recovery email message.
2. Setup a new email account, outside your current email service.
3. Clear cache, cookies, and sessions.
4. Restart the browser.
5. Login to your current email service, find, and open the email message.
6. Click on the link in the email message.
7. Setup a new Blogger account, based on the new email address.

Whatever you do when setting up your new Blogger account, please make sure to verify the email address - and setup recovery options, carefully.

>> Top

Blogger Accounts, And Domains Based On Google Apps

We've know, for a while, of the downsides of having a Blogger account that's based on an email address that's provided by a Google Apps based domain. Some people are unknowingly using email that is based on Google Apps administered service - and they are not even the administrators.

A few would be blog owners - or members (of a private or team blog) - are using Google Apps administered domains for their email. This detail never becomes relevant to them, until they try to join or setup a Blogger blog.

When I click on the invite link, and try to set up a new Google account, I get the message.

Blogger has not been enabled by the administrator of the domain xxxxxxx.edu.

What do I do, now?

When you are a prospective blog member or owner, and you are using a domain that you control and own - and are able to access the Google Apps administrator account for the domain - you may be able to enable the Blogger service, for the domain. If you are merely one user of the domain, where your email service is hosted, the situation won't be that simple.

If someone else controls the email domain, where you need to use Blogger, you have 2 choices.

• Convince the domain administrators to enable the Blogger service, in their domain.
• Setup a web based email account, outside your current service.
  • Recover control of the blog, using the current email address.
  • Transfer control of the blog, to a new Blogger account.

Neither solution is ideal.

Not all domain administrators, even for those domains which use GMail services for non "gmail.com" email addresses, believe Blogger blogs to be an essential service. Some believe blog publication to be a frivolous or insecure activity, and will intentionally block use of Blogger in their domains - possibly mandated by a Corporate Security Policy. These administrators are unlikely to attend to your need with any amount of urgency.

Some educational institutions or corporations, which are now using GMail in their private domains, may also consider use of non domain, or web based, email as suspicious activity. This may also present a challenge to you, when you need to use Blogger.

You'll have to make a personal decision, when you are faced with an email account that does not permit Blogger accounts. Just understand the possible reasons why the choice is necessary.

>> Top

Attention June 2012 Graduates: Transfer Ownership Of Your Blogger Blogs, Now

As you pack up your personal belongings, and close down your various student activities related to your college / university life, you're probably spending some time creating various traces, to point to your new life, which is now starting. One such activity would involve filing various "change of address" notifications, for people / services who communicate with you through postal mail, addressed to the college postal address which you use.

Similar to postal mail, you probably have a college email address, issued to you when you registered as a student. Hopefully by now, you have setup a non college email account, and are busy filling out change of address "notifications" for the many services which communicate with you through email. As you do this, you should think of your Blogger account, which owns your Blogger blogs.

Before you lose access to your Blogger account that's based on your college email account, setup a new Blogger account, based on your new non college email address. Then, transfer control of your blog(s), to your new Blogger account.

Don't delay - do this now - before you end up asking for help that can't be provided.

>> Top