Skip to main content

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.

Comments

Popular posts from this blog

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.

Free Domain Registration By "UNONIC" Is Fraudulent

Blogger blog owners, like everybody else, like to save money.

Some blog owners prefer to save money when registering a custom domain, for their blogs. We've seen several free domain registration services, providing what is claimed to be a two level Top Level Domain "co.xx" (where "xx" == various country codes).

The latest in this ongoing story appears to be "net.tf" - and 13 other "top level domains".There is also an additional free service offering third-level .tf domains, under the name United Names Organisation. They occupy 14 second-level domains, including .eu.tf, .us.tf, .net.tf, and .edu.tf. They are run by the same company as smartdots.com, and are given away as URL redirections.