Diagnose Problems Using Affinity Testing

When you go to the doctor to report a health problem, you'll likely tell him

Doctor, I have a pain.

and he will likely ask you

Where does it hurt?

If you tell him

My stomach hurts.

he will probably ask

When does it hurt?

and

How long has it been hurting?

None of these are formalities or mere protocol, they are systematic problem identification procedures. We diagnose problems with Blogger, using similar techniques.

If you write in BHF: Something Is Broken and report

My readers can't access my blog.

or maybe

I can't access Blogger!

you'll likely get similar questions.

If enough people report a similar problem and provide useful details, we can identify an "affinity" to the problem. This may help Blogger Support to isolate a segment in their code base, or an errant server in their network, that's causing your problems.

If you report

Some of my readers can't access my blog!

you might be asked

Where are your readers located, who can't access your blog? Where are your readers located, in general?

and maybe

What language do your readers speak?

and

What language is the blog published in?

and

When was this problem first observed?

and

When was this problem last not observed?

None of these questions are asked, by the "doctors" in the clinic, or in the Blogger Support forums, as an attempt to annoy you, or to show off. And as simple as they sound, they are actually lead ins to much more complicated diagnostics, or maybe to referrals to other specialists.

Affinity testing compares multiple tests, and asks which tests produce the same results. Similarly, differential testing compares multiple tests, and asks which tests produce different results.

One of my simplest "tools" which I may use to identify an affinity would be my simple 7+ link set. That set of 7+ links (7 base links - plus more links which I may add, varying according to your initial problem report) represents a carefully chosen set of addresses.

Some addresses, in the link set, are in the Blogger / Google hosting space - and others may be outside Blogger / Google. Systematic analysis of the results of trying each link, one after the other, can lead to any of several different diagnoses.

If you have readers complaining of a problem with your blog, you can email the list of links to your readers, and have them click on each of the links, and report results. If the problem comes and goes on your computer, you can click on each of the links, repeatedly. By combining and comparing the results, you can identify an "affinity".

If you are given that list of links, as a reply to your question, and you're able to say (for instance)

I can access only #4 and #5 ("0001100").

or maybe

I cannot access #2 and #3, but I can access #1, 4, and 5 ("1001100").

you are well on the way to a diagnosis. On the other hand, if you can only reply

Some of the links get me nothing.

you are not as well on the way to a diagnosis.

Blogger provides a simpler (and no more consistently observed) affinity dialogue, at the top of the "Post a question" wizard, in some forums.

• Your Blogs URL:
• Browser(s) used:
• Location:

When properly answered

Your Blogs URL: http://blogger-status-for-real.blogspot.com/
Browser(s) used: Firefox V3 / IE V8
Location: California USA

There are good clues, that may help the helpers, or Blogger Engineering, to identify a new problem - and may help them to help you faster. On the other hand, a frequently seen set of mildly amusing "answers"

Your Blogs URL: blogger-status-for-real.blogger
Browser(s) used: i dunno, it came with the computer
Location: planet earth

are less useful.

It's your choice what details to provide, to the forum helpers. In the same way, you get to chose whether to tell your doctor that you've started smoking, again.

>> Top

Blogger Templates Cannot Be Easily Validated, Using Public Diagnostic Tools

We see panic, exhibited by many blog owners, in Blogger Help Forum: Something Is Broken.

I used the W3 Template Validator, and got hundreds of errors! Is my blog broken?

This blog owner, like many others, does not understand the differences between W3 Standard HTML / XHTML, and Blogger HTML / XML.

The unpleasant truth is that, ever since Blogger released the Layout class templates, in 2007, Blogger has been providing templates that can't be successfully validated using HTML / XHTML standards. Blogger has a lot of features that don't validate, according to public standards.

That's not to say that the W3 Template Validator, and similar online analysis tools and code validators won't be useful, in helping you proactively check your blog for problems.

If you've tweaked your template, and / or added various HTML based accessories, you may find a few informative entries, in a typical validation report.

Upon examining the validation report for this blog, I can find more than a few references to various accessories and tweaks that I've made in the past, which I can identify. Some of the 498 errors (as of today) can maybe be fixed - but many can't.

If you want to look for problems with your blog, start by creating a test blog, using the same template that you have. Then, run the validation of your choice against your test blog. The report that comes from your test blog, you can use as a baseline.

Take your baseline report, and compare it with the report for your working blog. Unless you've done a lot of customisation to your blog, you'll find a lot more errors identified on both reports, than not. You can (maybe, should) fix the problems which are unique to your working blog - and you may have to walk away from the others.

Like the frustrations caused by referer spam, which you learn to live with, I may have to ignore some coding imperfections. Your blog may be the same.

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

Diagnosing The Mysterious bX Codes

One of the most misunderstood features of Blogger blogs is the mysterious bX codes.

Every day, we see the frustration

It says there's something wrong and I should give this "error code" so Blogger can fix it. What should I do? Where can I send the "error code"?

When you get a bX code, there's not a lot you can do, to directly diagnose the problem.

Excepting for diagnosing bX codes related to custom domain issues, your first step is to use Google Search, and target the complete code

bX-sp4hmm

Then see if someone else has reported that exact same code

bX-sp4hmm

.
After you use Google Search, you can help narrow down the problem - and maybe encourage other people to do the same.

You can identify which portion of your Blogger activity contributes to your observation of any specific bX code, using a differential analysis.

A differential analysis won't necessarily fix a bX code - most bX codes represent problems that originate deep within the Blogger code base. It may, though, help Blogger Engineering to identify the source of the problem.

Your details, added to similar reports by other blog owners, could make the difference between a problem that gets fixed in a couple weeks - or in a couple hours.

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

Blog Content, And Confusion About Blogs Locked After Detected Account Hacking

One Blogger mystery involves the varying periods of blog unavailability, after hacking activity is detected.

My blog just disappeared from my dashboard - and no, it's not listed under "Deleted blogs"!

When the owner mentions the notice about "suspicious" / "unusual" account activity, or having unlocked the account (by solving a CAPTCHA, receiving a phone message, changing the password) - and is advised to wait "24 to 48 hours" - many ask the obvious.

Is "24 to 48 hours" really accurate?

In reality, the legendary "24 to 48" hour time period is only a ball park figure - and both Blogger / Google, and the blog owner, contribute to the uncertainty.

The well known advice to "Wait 24 to 48 hours", after a Blogger account is locked for suspected hacking activity, is only an estimation of the waiting time, which the owner may have to endure. This is account / blog integrity verification.

There are several factors which can contribute to the accuracy of "24 to 48 hours" (which maybe should be stated as "one to two business days").

• Availability of essential Blogger / Google personnel.
• Current hacking activity level, and ongoing Blogger / Google workload.
• Blog content, which complicates hacking payload analysis.

We've referenced the first two factors (personnel, and hacking activity level) in the well known Blogger FAQ How long will it take?. The third involves detail which only the blog owner can provide. Many blog owners contribute to this uncertainty, in the development of their blogs.

There are several types of content, which hackers like to add, to blogs temporarily under their control.

1. Advertising - and similar shiny accessories.
2. Custom code - and various template tweaks.
3. Links to other blogs - and to websites outside Google address space.
4. Team memberships - and multiple blog owners.

All of these features, also added by the owner - and allowed (and encouraged) by Blogger - can require extra effort as a blog is validated, after detected hacking activity.

Blogger / Google security experts, in examining an account / blog, must look for features possibly added by the hacker. Security experts have no immediate knowledge what was added by the owner, long ago - as opposed to by a hacker, more recently.

Any advertising, custom code, external links, or team memberships, intentionally added by the owner, will contribute to time spent validating blog integrity.

• Leave a setting or tweak added by the hacker - and the blog remains a security risk, when returned to service.
• Remove a setting or tweak added by a blog owner - and the blog becomes broken, when returned to service.

Neither is desired, by the blog owners - nor by Blogger / Google.

More accessories and tweaks == more time spent by security experts == more time the blog remains offline, while the owner waits in uncertainty.

This uncertainty, added to delayed deletion caused by cache latency, leads to mystery.

All of this brings to mind the old adage.

KISS

Keep it simple, stupid.

>> Top

How You Should Backup Your Blog Will Depend Upon How You Plan To Restore It

We see signs of naivete, in Blogger Help Forum: How Do I?, from blog owners concerned with malware / spam deletions, and with other unexplained disasters in Blogger.

How do I backup my blog, to protect the contents against unfair spam deletions?

Not many concerned blog owners realise the first principle of backups, known by any experienced network administrator.

• Never plan a backup, without first planning the restore.

How you backup your blog depends upon several details.

• What problem do you expect, to require a backup?
• How do you plan to recover, from a problem?

One of the simplest solutions for a backup, which some Blogger experts will suggest, is to use the Export / Import wizard, in Settings - Other.

• Before disaster strikes, Export your posts and comments.
• After disaster strikes, simply Import your posts and comments, from a convenient backup.

Similarly, some experts may suggest backing up the template.

• Before disaster strikes, use the dashboard Template "Backup / Restore" wizard, to backup the template.
• After disaster strikes, use the wizard to restore the template.

There are many components of a Blogger blog - not just the comments, posts, and template.

• Accessories.
• Comments.
• Decorations.
• Gadgets.
• Posts.
• Layout.
• URL.

Before you plan how to backup your blog, you need to decide which of these features is most important to you, and what problem from which you wish to recover.

The accessories (decorations, gadgets) is one component of the blog which is most frequently missed, after a deleted blog is recreated / restored using a "comments / posts / template backup" restore strategy. Both graphic decorations, and XML based gadgets, may not be easily backed up, and may present a challenge when the blog is restored, or recreated.

XML gadgets, such as bloglists and linklists, may contain a lot of detail, which is installed into the blog one entry at a time - and there is no known way to automate a backup or restore of these gadgets.

Recovering the URL is one of the most subtle details, that may not always be considered by many blog owners. The URL is relevant in two ways. Most blogs which are important enough, for the owner to want to backup, have acquired reputation - both with people (readers, subscribers, and viewers), and with search engines.

Some blogs will link the various posts to each other - as I do with this blog. In either case, the recovered blog is not as useful, unless the URL is also recovered.

If the blog is deleted by Blogger - or by the owner - the URL may not be available, for blog recovery. When Blogger deletes a blog as a suspected abusive content host, the URL is locked to the blog. The only way to recover the URL is to have the blog reviewed, and restored to availability.

When a blog is deleted by the owner, the blog must be restored by the owner - within 90 days after deletion. In either case, a backup is useless.

If you have a personal blog, containing just posts (and maybe comments from known family or friends), backing up the comments and posts makes sense. For a publicly known blog, containing various accessories, and having a known URL, you'll want to plan your backup / restore strategy using a bit more effort.

>> Top

Blogger Blogs And Commenting Permissions

Not all Blogger blog owners know that the ability to comment, like the ability to publish and read posts, is a privilege which they control - and a responsibility which they need to control, carefully.

Any blog owner who wishes to publish a blog, and not be subject to frequent deletion of the blog, as a suspected malware or spam host, needs to understand the responsibilities, and the risks.

There are levels of ability to post comments to a blog, which you select from the dashboard Settings - "Posts and comments" wizard. Protect yourself, if you allow comments.

• Anyone - includes Anonymous Users.
• Everybody with a Google, or an OpenID, account.
• Everybody with a Google account.
• Blog members only.
• Comments disabled.

Choose this setting with great care.

If you allow comments by "Anyone", prepare to deal with the spam. Note that anonymous users can post either anonymously, or using "Name / URL" tags, at their discretion, with "Anyone" selected. "Name / URL" does not provide authentication. "Anyone" means anyone, period.

Besides "Who can comment?", you may also control comment publishing using CAPTCHA (aka "word verification") screening, and using comment moderation. These settings, like "Who can comment?", are part of the Settings - "Posts and comments" wizard.

Every blog owner, hoping for any visibility in the Blogosphere, needs to choose these settings carefully - or risk being buried by spam.

• Who can comment?
• Comment Moderation.
• Comment Notification Email.
• Show word verification

Comment Moderation, and Comment Notification Email, together, provide 2 settings which can bury your email Inbox, depending upon activity of commenting on your blog. Choose these settings wisely.

If you allow spam comments without control, you may later find yourself asking for help, in Blogger Help Forum: Something Is Broken

Help me! My blog was deleted by Blogger!

Protect your blog, and your blog's future, by allowing comments, responsibly.

>> Top

The Content Of Your Reading List Is Your Responsibility

Occasionally, we see an odd problem report about Reading List content, in Blogger Help Forum: Something Is Broken.

How did this blog get into my Reading List? I did not Follow this blog!

Most people will not, knowingly, Follow a spam blog. This is one reason why Following is so popular - each blog owner, and blog reader can easily bypass, and actively block - spam. Spammers have, however, found devious ways to convince people to Follow them.

Nobody will, intentionally, Follow a spam blog. If we unintentionally Follow a blog which is owned by somebody gullible to the spammers suggestions, it's not difficult to identify, and stop Following, any blogs owned by gullible people.

You can, using the right reporting procedure, identify the blogs which offend you. It's possible that Blogger / Google will, given the right complaints, remove such blogs.

• Any action taken upon your report of problem blogs is subject to delay - and due process of law - before any results will be seen.
• The content which offends you may not be provided in a Blogger blog. Google has no power over non Google hosted websites.
• Any blogs removed as a result of your complaints will be replaced, in the spam blog cloud, which you are seeing, thanks to the blog which you are Following.

When you see content which offends you, in your Reading List, the proper resolution will be simple.

• Find, and remove, the blogs which you are Following - and which provide the problem content presence in your Reading List.
• Report the blogs which you are Following - not the blogs / websites which provide the unwanted content.

You may, at your discretion, add a third step.

• Report the blogs or websites which provide the unwanted content.

But do the third step, as a third step - not as the only step. Report the problem blogs - as Step #2 - here, or in Blogger Help Forum: Something Is Broken. Be part of The Solution - not The Problem.

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

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.

Before Changing Your Custom Domain Published Blog, To Another Custom Domain, Do Some Research

As custom domain publishing becomes more popular, and becomes simply one more feature to add to your Blogger blog, some blog owners decide that the domain that they are using, right now, is not to their liking. Fortunately, with a Blogger blog, the process of changing your domain to another is not complicated - hoping that you have the right tools, and make the right decisions.

• Publish the blog back to BlogSpot.
• Use "Buy a domain" (if possible), and publish the blog to the new domain (as available).

All that being possible, there is a third step which many blog owners manage to overlook - until long after they have completed Step #2.

Since one of the features of custom domain publishing is to increase page rank / reputation / visibility by publishing the blog to a non BlogSpot URL, the vast majority of all Blogger blog owners, when changing the blog from one custom domain to another, will do well to plan a third step.

• Forward the current domain to the new published URL.

Too many times we see the plaintive cry in Blogger Help Forum: Something Is Broken.

I just bought a new domain for my blog - but the previous URL is now 404!

This is a common complaint, for some blog owners who do not think the process through, before starting the domain swap.

For too many blog owners, the third step is not, at all, obvious.

But how do I forward the domain?

Too many custom domain owners don't know how to use the Domain Manager wizard provided by the registrar - or (in the case of "Buy a domain" customers) have not even setup the Google Apps domain manager desktop account, which provides access to the Enom or GoDaddy Domain Manager.

For these blog owners - and any blog owners contemplating a domain change - I'll add a fourth step to the process.

• Do some basic research - find out how to access, and how to use, the Domain Manager wizard.

And do this new First Step before you need to report

I just bought a new domain for my blog - but the previous URL - and all my search engine hits - are now 404!

and preferably before starting

• Publish the blog back to BlogSpot.
• Use "Buy a domain" (if possible), and publish the blog to the new domain.

After you properly complete the above procedures, don't expect to see an immediate transfer of page rank, reputation, and visibility to the new published URL. You need to plan ahead, and consider the issues, when changing domains - just as you would plan the rename of the blog, and as you would plan the custom domain migration. You'll find that changing the custom domain published URL involves issues from both of the latter changes.

>> Top