Custom Redirects, And The Mobile Template Redirect, Are Not Compatible

We've recently seen a few reports about problems with custom redirects, in Blogger Help Forum: Something Is Broken.

I want to redirect my blog URL to a static home page. With a redirect in place, mobile computer users can't access my blog. Mobile browsers display an error, mentioning too many redirects.

This problem is being reported by owners of blogs both published to BlogSpot, and to non BlogSpot domains. When published to a non BlogSpot domain, the problem is present even for domains properly setup.

Some advice, given in the forum, suggests use of forwarding, instead of referral, as a solution. This advice is a problem, for 2 reasons.

• Forwarding cannot be used with blogs published to BlogSpot.
• Forwarding is not a good solution for custom domain publishing.

Right now, there is no solution for this problem - though there is a workaround. Blogger Support is aware of the problem - but it's not certain that a solution will be immediate.

For blogs published to BlogSpot, there are just two choices.

1. Disable the redirected home page, and do without the custom home page.
2. Enable the custom redirected main page, and do without mobile access to the blog.

For blogs published to a custom domain, there are, supposedly, three choices.

1. Disable the redirected home page, and do without the custom home page.
2. Enable the custom redirected main page, and do without mobile access to the blog.
3. Use forwarding, instead of referral, to redirect the domain to the blog.

Forwarding comes in two versions, with differing effects from the two versions. Neither version of forwarding is beneficial, to Blogger blogs.

• DNS forwarding results in the blog being indexed under the BlogSpot URL, by the search engines. The blog's readers will be able to use the (forwarded) domain URL, to access the blog - but all search engine references will mention the BlogSpot URL.
  
  With some access to the blog through the BlogSpot URL, and other access through the domain URL, blog reputation will drop, similar to blogs newly published to a new URL. Both reputation and traffic will do the same.
• Frame forwarding results in the blog being visible within an IFrame. No indexing of the blog, by the search engines, will take place, with blog contents visible inside an iframe. Search engine reputation will drop even worse with DNS forwarding.

Not all registrars offer both versions of forwarding, so you may have to take what they offer - and accept the resulting loss to the blog.

As a workaround, until the problem is fixed, you can return to the previous technique for making a static home page.

Basically, blog owners may have to choose between having a custom home page (for desktop access), and having the blog accessible through mobile browsers (for mobile access) - or using the workaround. And everybody has to wait, patiently, until Blogger Engineering can come up with a better solution - to make custom redirects, and the mobile browser redirect, work together.

>> Top

Blog Owners Report "isExperimental: Required field must not be blank" When Using Blogger

We're seeing a number of blog owners, reporting a new problem with their Blogger dashboards, in Blogger Help Forum: Something Is Broken.

I am seeing an new error in the Live Preview section of the Template Designer.

The following errors were found:
isExperimental: Required field must not be blank

Upon examination of the URL window in the browser, the source of the problem is seen.

draft.blogger.com/blogger.g?blogID=xxxxxxxxxxxxxxxxx#templatehtml

It appears that we are seeing one more reason why routine use of Draft Blogger is not a good idea.

People who are seeing the "isExperimental" error have only one choice - stop using Draft Blogger for template customisation.

Many of the blog owners reporting this problem have previously selected the option to use Draft Blogger, by default. When this is the case, returning to standard (non Draft) Blogger is not complicated.

• From the dashboard home page, next to the blog list, find the gear icon.
• Click on the gear, then on "Edit User Settings".
• On "Edit User Settings", and under "General", de select the option to "Use Blogger Draft".
• Log out of Blogger, clear cache, cookies, and sessions, restart the browser, and log back in again.

Having reset the redirect option (if necessary), always login using "www.blogger.com", instead of "draft.blogger.com".

>> Top

The Text Gadget Is Broken

For over a week, we've had anxious blog owners unable to create or update the Text gadgets on their blogs.

The "Save" button is not working, on my Text gadget!

or maybe

I see Javascript void(0) when hitting Save!

Blogger actually fixed this problem, earlier this month - and it broke again, shortly afterwards. Not everybody understands that seeing "javascript:void(0);" is a symptom of the problem - not the problem itself.

This problem, fortunately, has a reasonably effective workaround.

The HTML / JavaScript gadget, and the Text gadget, are virtually the same gadget.

If you add an HTML gadget, using "Add a Gadget" - and you select "Rich Text", when setting the gadget up, - you will have a Text gadget.

Just be careful - when you have a Text gadget, the place where you selected "Rich Text" will read "Edit Html". If you click on "Edit Html", you'll have an HTML / JavaScript gadget, which will then read "Rich Text".

If you want a Text gadget, make sure that the gadget label reads "Edit Html". It's that simple.

This will not resolve every problem.

• The inability to update existing Text gadgets continues to be a problem.
• The similar inability to update Linklists has no workaround.

This is simply a small workaround - but a useful one, where applicable.
>> Top

Making Blogger Run Properly, On Our Computers

One of the biggest problems with Blogger, right now, is how we allow Blogger to run, on our computers.

We protect our computers from threats - known and unknown - using layered security. Right now, some of us are protecting ourselves too carefully - and we are seeing the results, with problems in Blogger.

The Blogger application, which we use to maintain and publish our blogs, runs on our computers.

We get Blogger program code from the Blogger servers, and we run the Blogger code on our computers. The Blogger code includes two essential components - cookies (settings, which control how the programs run), and scripts (the programs themselves).

If we want to run the Blogger code on our computers, we have to let Blogger and Google load cookies, and run scripts, on our computers.

If we can trust Blogger to host our blogs - on their computers, we need to trust them to run their code - on our computers. We need to configure our cookie and script filters, on our computers and networks, to trust Blogger and Google.

• In our browsers.
• On our computers.
• On our networks.

Cookie and script filters are found in many places - and all filters must be configured, properly. Click here for instructions on configuring your browser filters.

If Blogger Engineering is to spend their time, developing and maintaining Blogger, we have to support their efforts. We have to setup our computers properly - so Blogger will run, properly.

>> Top

Confusion From The Message "You have logged out from another location."

This month, we have a small flood of reports, from blog owners who are seeing the latest monolithic error.

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

This error has actually been reported previously - but in smaller volume - for some time. It appears to be similar in nature to a previously reported problem, "Conflicting Edits".

The problem appears to possibly affect anybody who has logged in to Blogger - and it appears to be persistent, and has inspired imaginative measures, from some blog owners.

The basic error condition, "You have logged out from another location.", has actually been around for many months.

Advice from Blogger Support staff, as occasionally provided, is reasonably simple.

If you are still receiving this error please clear and cookies, refreshing the page and log-in again.

Observing a lack of consistent success, from the latter advice, I recommend a more deliberate procedure.

1. Check cookie and script filters.
2. Clear cache, cookies, and sessions (all 3).
3. Restart the browser.
4. Click on the link below, to login to Blogger.

https://www.blogger.com

However one attacks the problem, when seen, it's not producing a lot of happy blog owners. Unfortunately, until Blogger Engineering permanently fixes the underlying problem, the temporary solution requires action by the blog owners affected.

If you follow the above advice, and continue to see this error, I suggest that you try a combination of affinity testing and of differential testing - then report the problem and a summary of your diagnostic tests, in Blogger Help Forum: Something Is Broken.

The anger expressed by some blog owners, repeatedly seeing "You have logged out from another location.", appears to resemble what was seen after the Blogger melt down of May 2011. That problem started during the week of May 9 - 13, when Blogger blog maintenance was impossible for over a week.

I, myself, am used to seeing this message - once or twice a week. I almost always have one or more browsers logged in to Blogger / Google, with various tabs opened to Blogger, FeedBurner, GMail, Google Groups, and / or Webmaster Tools.

With multiple tabs opened to various Google applications, it's a fairly simple (though not enjoyed) task to simply close all Blogger tabs, open one new tab targeting "http://www.blogger.com", and watch as the login session present under FeedBurner, GMail, Google Groups, and / or Webmaster Tools, refreshes into the newly opened Blogger tab.

The problem this month appears to be more persistent than my personal observations - and supposedly continues even through browser, and computer, restarts. Follow the above advice, please - then report your observations in detail. And please, be patient with the helpers who respond.

>> Top

CAPTCHA Verification Is Broken, For Some Blogs, In Various Applications

We're seeing a number of problem reports, in Blogger Help Forum: Something Is Broken, about various problems which involve CAPTCHA verification processes.

The symptoms are fairly diverse.

• Some blog owners report problems with commenting, on their blogs.
• Some report problems with high posting volumes.
• Some report problems getting abuse review requested, for their blogs falsely accused of hosting abusive content.

The reporting volumes, and perceived urgency, for each case, will vary.

The known problems involve various bX codes, issued in place of the CAPTCHA form.

• An unverified code is being seen, by people trying to post comments, on blogs using CAPTCHA screening.
• Blog owners are reporting various bX codes, when trying to post high volume blogs.
• Other blog owners are reporting "bX-niui1k", when trying to request spam review, from the dashboard "Deleted blogs" list.
• It's possible that there are other CAPTCHA applications, also seeing bX codes.

The audience observing the bX codes will differ - because the relationship of the people needing to use the CAPTCHA, and the volume of CAPTCHA use by the affected people, will differ.

People observing a bX code, when trying to post a comment, will be guests on blogs which use CAPTCHA screening - since blog members and owners are not subject to comment screening. CAPTCHA screening is optional for comment moderation, in general - and it's possible that many blog owners are not using CAPTCHA screening on their blogs.

It's also possible that only blogs which use the full page and popup comment forms are vulnerable, to this problem. The report volumes involving bX codes involved with comment moderation are low - and this will make affinity analysis difficult.

People observing a bX code, when trying to post at high volume, will be blog owners who post frequently. The reports of this problem are low to medium volume - possibly because many blog owners avoid posting excessively. This may be because we have observed that repeatedly solving a CAPTCHA will be inconvenient.

The people who report this problem are fairly insistent that this problem needs to be solved. Since the bX code is observed repeatedly (once for each high volume post attempted), by the blog owners affected, this case will involve the most controversy. Several blog owners have reported seeing differing bX codes.

People observing a bX code, when trying to submit an abusive blog review request from the "Deleted blogs" dashboard list, will be blog owners whose blogs were deleted or locked, spuriously, for abusive content (aka "spam hosting"). These people will post in the forums, and can be helped fairly easily, by our promptly offering a manual review, submitted to Blogger Support.

This case represents the most frequently reported symptom - but since the people affected can be helped with minimum fuss - and since this case is only observed once for each blog involved, this case will involve less controversy. This case has been reported, as noted, consistently producing the "bX-niui1k" code.

It's possible that CAPTCHAs are used in other unidentified applications - and we may yet have other cases to discuss, if the base problem is not resolved fairly promptly. Blogger Support is currently aware that there is a problem - and hopefully, where the problem lies.

>> Top

Post Editor Problems With Blog Owners Using Internet Explorer V8

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

The symptoms are varied, in detail.

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

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

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

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

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

Google stopped supporting Internet Explorer V8, in 2012.

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

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

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

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

The solution, for this problem, requires your action.

>> Top

Mail-To-Blogger - July 2012

We have seen a significant number of reports, in Blogger Help Forum: Something Is Broken, again mentioning inability to post to our blogs using EMail / Phone / SMS. The problem appears to have started several days ago - but was quiet for a while, and has been rather noticeable today.

Blogger Support posted last Thursday, acknowledging the problem - but since then, the problem appears to have gotten worse.

Oddly enough, I conducted my standard functionality test, and sent a message at 18:00 my time, which posted to my test blog at 18:16. Normal latency would be 1 - 2 minutes, not 16 minutes. Before posting, I was forced to update my MTB "secret word", as I examined my settings and found that the "secret word" had been previously cleared.

We have a rollup discussion where we are requesting diagnostic details, from blog owners observing the problem.

1. What is the URL of the blog?
2. When did you, initially, observe a problem?
3. When did you, most recently, observe a problem?
4. When did you, most recently, not observe a problem?
5. Do you receive an email refusal (aka "bounce back message"), or does the email / message simply disappear?
6. How long has it been since you last changed the MTB "secret word"?
7. Do you post using GMail based email, Non GMail based email, or Phone / SMS?

If you're able, please provide reports of your involvement with this problem.

---

(Update 7/30): Blogger Support has reported the problem as fixed.

Update, 7/30: This has been fixed.

---

>> Top