Recovering From A Corrupt Template - Persistence

Of the many Blogger Mysteries that confound blog owners and readers, none are more obscure than the many bX codes.

Some problems, reported in Blogger Help Forum: Get Help with an Issue, start so innocently.

As I edited the Template HTML, I saved my changes - and the bX error suddenly appeared.

Each different bX code refers to a different problem, with Blogger in general. Of the bX codes that refer to template corruption, each different bX code may refer to a different template corruption problem.

When a template corruption problem can be reset, the resetting process may involve repeated use of one or more dashboard pages.

Different problems may enable - or prevent - use of a different dashboard page. For problems with multiple causes, you may have to use each different wizard, persistently.

1. The Template Designer page.
2. The Template page.
3. The Template Editor ("Edit HTML") page.
4. If the blog is not operational, you start again.

Unfortunately, some problems may prevent use of all 3 pages. For the problems that permit use of one or more pages, you try each available page, repeatedly, until the blog becomes operational.

To access each page, you may need to bypass the dashboard menu.

The Template Designer page.

The Template Designer is used for one task - "Remove customizations".

The Template Designer.



"Remove customizations" may be the simplest reset that you may try - when possible. Some customizations, when removed, may enable subsequent use of the Template page, or the Template Editor.

The Template page.

The Template main page is used for two tasks.

1. Backup / Restore the existing template.
2. Get a new template.

The Template main page.



Some problems, when reset using the Template main page, may enable subsequent use of the Template Designer, or the Template Editor.

The Template Editor ("Edit HTML") page.

The Template Editor ("Edit HTML") is used for two tasks, as an alternate to the Template main page. Also, it may be used to reset any "rgba" colour combination problems.

1. Backup / Restore the existing template.
2. Get a new template.

For template corruption problems that prevent use of the Template main page, the Template Editor - combined with a second blog, where a clean template is developed and tested - can be used.

The Template Editor (aka "Edit HTML").



Some problems, when reset using the Template Editor, may enable subsequent use of the Template Designer, or the Template main page.

If the blog is not operational, you start again.

If you get a new bX code, you repeat the above sequence. Some problems, with multiple causes, may require repeated retries.

In extreme cases, you may end up creating a new blog at the URL.

---

Some #Blogger template problems, which lead to a bX code display, may have multiple causes - and all causes may require solution, to make an affected blog operational. With some causes preventing solution of others, a repetitious use of the various dashboard pages may be required - to solve some template corruption problems.

Read More

Some bX Codes Caused By Zero Alpha ("rgba") Value

We're seeing a few reports of bX codes, that are not solved by simply resetting the template - and do not involve the mysterious "500 Internal Server Error".

In some cases, the blog owner may see a bX code when trying to use "Configure Blog Posts", or another Layout gadget wizard. If the blog itself can be viewed, and Template HTML Editor is usable, the bX error may come from use of a "0" Alpha color setting.

Blogger Engineering is aware of the problem, and has suggested that a fix is being developed. While we await the necessary fix, we may need to work around the problem.

The suggestion by Blogger Engineering is that we use a "Transparent" option, instead of "0" alpha value.

It seems that this issue is triggered by color variables with a value that has zero alpha, e.g. 'rgba(0, 0, 0, 0)'.

Some gadgets, and template sections, have the "transparent" selection in their color setup. Not all have this option, however. Some template CSS rules are not so easily edited.

The problem here is the "rgba" 4th value of "0" - ie, the "alpha" "0" value. The simplest solution is to change the "0" to a non zero value - without changing the "rgb" values.

The simplest solution, to get "Configure Blog Posts" or any other affected gadget usable, may be to use Template Editor, and change the values, directly. Look at every CSS rule, that has an "rgba" setting - and look for a 4th value of "0".

• For "rgba(0, 0, 0, 0)" - Change to "rgba(0, 0, 0, .1)".
• For "rgba(255, 255, 0, 0)" - Change to "rgba(255, 255, 0, .1)".
• For "rgba(255, 255, 255, 0)" - Change to "rgba(255, 255, 255, .1)".

A transparency setting of ".1" should be visually close to "0" - and should get the blog in question back online and updatable. And after Blogger Engineering fixes their gadget / template editor code, to accept the "0" value - and if the ".1" creates a noticeably unacceptable condition - this can be corrected, when necessary.

It's possible that this error, being seen, is part of a larger problem. You may need a persistent solution.

---

Some #Blogger bX codes, being seen in the forums right now, do not appear to involve terminal template corruption, and the mysterious "500 Internal Server Error". Some bX codes can be easily corrected, when they involve a "0 alpha" value (a CSS color rule involving an "rgba" setting).

When the Template Editor is usable, a simple search and replace for "rgba(nn, nn, nn, 0)" to "rgba(nn, nn, nn, .1)" may be sufficient to correct the error.

Read More

Recovering From The Corrupt Template / "Error 500"

We're seeing a few reports, this week, in Blogger Help Forum: Get Help with an Issue, about blogs with broken templates.

I tried to log on to my blog, and it shows up an error message. I've done it several times on different browsers, but no change: the error code is bX-uukqqu.

It appears that the "bX-uukqqu" is from the owner attempting dashboard access. Trying to view the same blog, I see the ubiquitous "bX-v2vqfh".

Both codes reference blogs which show up, in an HTTP trace, with the monolithic message "500 Internal Server Error" - and tells us that this is one more blog with a broken template.

If you, the owner of a blog with a broken template, can access the Template dashboard page, you may be able to recover the template.

Some blog owners report that adding a Template Backup / Restore has helped to resolve their own bX code / "Error 500".

1. Backup the template ("Download full template").
2. Get a clean Blogger standard template.
3. Restore the template ("Upload" the template that you just downloaded).

If you're lucky, your version of the "bX-uukqqu" (dashboard) / "bX-v2vqfh" (public) can be resolved, by a quick template download then upload.



You may need direct access to the Template page, bypassing the dashboard menu - though if you can view the blog, the "Design" navbar link will provide you that ability. If you can't access the Template page at all, you may be able to clear some bX codes, by using the Template Editor aka "Edit HTML".

If any of this works, your blog will be back in service. If not, you will at least have a backup copy of the template.

If the template is still broken, you now have three choices.

1. Leave the blog as it is now, broken - until Blogger Engineering finishes diagnosing and fixing the actual cause of the template corruption.
2. Get a fresh new template. When Blogger Engineering finishes diagnosing and fixing the actual cause of the template corruption, you can try restoring the template copy that you just backed up.
3. Try a persistent solution.

And whether this works - or not - or even if you can't use it, right now, you can have a template backup. And one day, this backup may be useful.

---

A few Blogger blog owners, reporting bX codes when trying to access their dashboards, have found that accessing the Template page directly, then doing a quick back / restore, may clear the bX codes. This suggests that Blogger Engineering is beginning to test solutions to the ubiquitous "Error 500" broken template problem, that have been afflicting blog owners for some time.

---

Read More

Recovering A Broken Template, Using "Edit HTML"

I have, for a long time, recommended regular template backups, for those who like to tweak the template.

Normal backup uses the "Backup" wizard, on the dashboard Template page. When backed up, an XML file, containing the template code, is extracted and saved locally. To restore, the "Restore" wizard is used and a previous Backup XML file selected.

That's how Backup / Restore should work - but it isn't always that easy.

With the current wave of bX codes, being used to diagnose the "Error 500", the Template dashboard page may not be accessible.

This is the case even attempting direct access, using the navbar "Design" link, or a hand generated equivalent.

With some blogs, the Template Editor may be OK - with the Template page broken.

For some blog owners who cannot use the dashboard Template page, the Template Editor aka Template "Edit HTML" may be accessible. This will require using a hand generated URL - since there is no direct link to the Template Editor.

If the Template Editor can be accessed directly, the blog owner may be able to continue.

1. Access the Template Editor for the broken blog, in one browser window.
2. Setup a new blog, using a clean template, in a second browser window.
3. Access the Template Editor for the new blog.
4. Copy the new blog template, to the broken blog.
5. Save the now recovered current blog template.
6. Refresh the post template.
7. Clear cache, cookies, and sessions, restart the browser, and try again.

The blog owner has a possible solution, in this case.



Access the Template Editor for the broken blog, in one browser window.

Use a hand generated URL, to access the Template Editor. If you can do this much, you are well on the way to getting your blog back.

If you truly feel the need, you can backup what's there, before you paste over what you have. Ctrl - A then Ctrl - C to copy - then Ctrl - V, into a new text document - that you can save, at your convenience.

Setup a new blog, using a clean template, in a second browser window.

Blogs are free, so make a new one. Select the "Simple" template, for best results.

Access the Template Editor for the new blog.

For the new blog, you can use the dashboard menu, and Template - "Edit HTML".

Copy the new blog template, to the broken blog.

With the Template Editor window for the new blog, containing a valid template, copy its contents (Ctrl - A then Ctrl - C) - into the Template Editor window for the broken blog (Ctrl - A then Ctrl - V).

Save the now recovered current blog template.

Hit "Save template". And say a brief prayer.

Refresh the post template.

This may not be necessary - but you should consider it. It has saved a few blogs.

Clear cache, cookies, and sessions, restart the browser, and try again.

This is always a good idea, when clearing bX codes.

It's a workaround - not perfect, but it may get the blog going again.

This is not a perfect solution. If you are tired of the bX codes, and if this will get your blog operational, you may find it useful, however. It's also possible that this error is part of a larger problem - and you need a persistent solution.

If you have a template back up, you can apply that after the blog is back in service. And your readers have stopped emailing you with angry complaints. Just use a clean backup.

And test your tweaks, going forward, more carefully.

---

Some bX codes, being used to diagnose the "Error 500" condition in #Blogger blogs with broken templates, affect the dashboard Template page. Blogs which have broken Template pages cannot be recovered by getting a new template.

In some cases, with the Template page unusable, it may be possible to directly access the Template Editor - then paste a separately developed clean template into the "Edit HTML" window, and correct the problem.

Read More

bX Codes, Diagnosing "Error 500", Being Reported

We're seeing a few reports from blog owners, in Blogger Help Forum: Get Help with an Issue, with blogs being inaccessible.

My blog can't be seen at all, it just says error when I'm trying to open my blog. I also can't edit anything, like HTML or Template.

When the blog is viewed, it will issue one of several bX codes. So far, I've identified bX-3o92c2, bX-ppgc07, bX-tqn3zr, bX-v2vqfh, bX-vg1g6a. When the blog is viewed, using an HTTP trace, the trace will terminate, showing an old friend.

Error 500 Internal Server Error

What we appear to be seeing is multiple bX codes, being used to diagnose the various causes of the "Error 500", which has long plagued Blogger blog owners.

The "bX-v2vqfh" and other errors appear to be "500 Internal Server Error".

Here, we see a "bX-vg1g6a".

And an HTTP trace, for the same blog, shows the ubiquitous "Error 500 Internal Server Error".



So, the blog owner should get a new template - or restore from backup.

The simplest solution, to the "Error 500" has been to restore the template, from a recent backup - hoping that you have a usable backup. If a backup is not available - or if the blog, with the backup applied, also returns a bX code - you must get a new template.

The fortunate blog owner, able to login to Blogger with the right account, will have a relatively simple task.

1. Click on the "Design" link in the navbar.
2. Choose a new template - or restore from a previous backup.
3. Use "Edit HTML", and reset the post template.

If the blog has a custom template, that cannot (should not) be trashed, and the Template page can be accessed, a backup before getting a new Blogger template - and a restore after - may provide relief.

In either case, you will need to use the dashboard Template page - then reset the post template, using Template "Edit HTML".

In some cases, the dashboard can't be accessed. In this case, we must (with some effort) access the Template page, directly.

Possibly a little effort may be required.

1. Extract the BlogID, from the navbar "Design" or "New Post" link.
2. Build a Template page access URL.
3. Access the Template page, using the direct URL.
4. Choose a new template - or restore from a previous backup.
5. Use "Edit HTML", and reset the post template.

If the navbar link can't be used, a little more work is involved.

1. Find a cached copy of the blog, before the template broke.
2. Extract the BlogID, from the cache source code.
3. Build a Template page access URL.
4. Access the Template page, using the direct URL.
5. Choose a new template - or restore from a previous backup.
6. Use "Edit HTML", and reset the post template.

Finally, if possible, recall what changes you made, immediately before the problem was observed - and avoid repeating those changes.

Note that some blogs absolutely won't provide access to the Template page - but they may, to the Template Editor aka "Edit HTML".

---

It appears that #Blogger Engineering, in an effort to diagnose the annoying "Error 500 Internal Server Error", has recently activated or added a series of bX codes - which are being reported by various blog owners.

We were some time ago advised to have the owner get a new template, when encountering the "Error 500".

Read More