Social Icons

Pages

Showing posts with label HTML Gadget. Show all posts
Showing posts with label HTML Gadget. Show all posts

Monday, 9 December 2013

Problems Adding / Editing The HTML And Text Gadgets

We're seeing a few reports, in Blogger Help Forum: Something Is Broken, mentioning problems adding or updating the HTML and Text gadgets. The most common symptom is very simple.
When I try to update the gadget, all that I see is
javascript:void(0);
In this case, we have to first explain that "javascript:void(0);" is not the problem - it's simply a symptom of the problem.

Once we explore the problem itself, we see various possible causes.

The base cause for problems with the HTML / Text gadget is simple - the script which processes gadget updates provides no diagnostics when detecting errors.

If you were to update a post, or the template, with bad HTML, you'd see some error message, indicating that your changes are bad.

Both Post Editor and Template Editor provide some diagnostics, when errors are detected. With the HTML / Text Gadget, the script issues no error messages, it simply stops.

Instead of "javascript:void(0);" displaying for a fraction of a second, as the update is saved and the window closes, the blog owner is left looking at
javascript:void(0);
until he hits "Cancel" in confusion.

The HTML / Text gadget has been observed to have various problems, which prevent changes from being properly saved.
  • Bad HTML, when accidentally in HTML mode.
  • HTML / JavaScript code which contains line breaks in the wrong places.
  • Bad HTML code, when intentionally entering an HTML gadget.
  • Gadgets with blank titles.
  • Layered security, which blocks the gadget update scripts from running.
  • Trying to use a non supported browser version.


Blog owners who are not observant, when updating the gadget, may accidentally be in HTML mode. Rich text, containing HTML significant characters, will be a problem.

HTML / JavaScript code is sensitive to line breaks in the wrong places in the code. Blog owners, accidentally or intentionally inserting line breaks, can cause a problem.

HTML / JavaScript code, in general, is syntax sensitive. Bad code will always be a problem.

Gadgets with blank titles will cause a problem, when using some browsers. If a gadget with a blank title is specifically required, it may be possible to use a null title, instead.
<!-- -->

Inappropriate use of layered security may block cookies or scripts, and prevent the gadget from updating.

The gadget, like every other Blogger feature, must be updated to support newer browser versions. It will likewise be updated periodically, to remove support for older browser versions. Non supported browser versions will frequently cause problems.

Some of these error scenarios should be more clearly identified, by the script - but not all can be identified. Attempting to save a gadget with a blank title, for instance, should produce a stern warning
Blank titles are not accepted.
Unfortunately, HTML syntax errors generally can't be consistently diagnosed, with any detail.

The best solution here is for the blog owners to be aware that the gadget operates this way, when being updated. Some cautious effort must be made, when updating the gadget.

It's possible that problems updating the gadget, like many Blogger problems in general, can be best diagnosed using affinity testing, and / or differential testing.

>> Top

Sunday, 3 November 2013

Updating A Text Gadget, On Your Blog? Be Careful!

The schizophrenic nature of the HTML / Text gadget continues to confuse some blog owners.

Recently, we're seeing claims about broken Text gadgets, in Blogger Help Forum: Something Is Broken.
I hit the Save button, and nothing happens! Why is my Text gadget not working??
Too many blog owners are causing their own problem, because of confusion about the caption in the gadget update wizard.

The header of the HTML / Text wizard is the only visible difference, between the "HTML" and "Text" gadgets.

You'll see "Configure HTML/JavaScript" (for an HTML gadget) or "Configure Text" (for a Text gadget), as the gadget header. The rest of the gadget will be the same, for both gadgets - and this is why some gadgets, being updated, appear to be broken.

The difference between entering HTML, and Text - using either the "HTML" or the "Text" gadget - will be seen in the caption, to the far right of "Content".

The difference between entering HTML, and Text, is not relevant to the actual gadget being added or updated. This problem exists for both "Configure HTML/JavaScript" (for an HTML gadget) and "Configure Text" (for a Text gadget).

The caption will read either "Edit Html", or "Rich Text" - for both "Configure HTML/JavaScript" (for an HTML gadget) and "Configure Text" (for a Text gadget).
  • If you want to add / update code (HTML / JavaScript), you will want the caption to read "Rich Text".
  • If you want to add / update text (Rich Text), you will want the caption to read "Edit Html".
Examine the formatting toolbar, to the left of the caption, as you click on the caption, to understand this.

Here are 4 views, showing the same gadget:


This is the HTML gadget, in HTML mode.

This is the HTML gadget, in Text mode.

This is the Text gadget, in Text mode.

This is the HTML gadget, in HTML mode.


Why is this relevant to the problem, being discussed? Just this - HTML is simply fancy text, with tags (special keywords and symbols). The tags make the difference, between HTML and text.

When you enter HTML, the tags have to be entered properly, in pairs and in the right sequence. If HTML tags are not entered properly, you can have various problems with the blog, as displayed. One of the possible problems is the long known dropped posts / sidebar section.

When you enter HTML improperly, in "HTML" mode in post editor, you get various diagnostic error messages - and you are instructed to fix your tags. When you enter HTML improperly, in "HTML" mode in the HTML / Text gadget, the "Save" button becomes in operative - and you think that the gadget is broken.

When you enter Text, which contains HTML, and you enter the HTML improperly - and you are accidentally in HTML mode - you have a problem. Remember.
  • If you want to add / update code (HTML / JavaScript), you will want the caption to read "Rich Text".
  • If you want to add / update text (Rich Text), you will want the caption to read "Edit Html".
This is how the "HTML" and "Text" gadgets work.

If you add a Text gadget to your blog, the caption will read "Edit Html" when you are adding text. If you click on "Edit Html", you will see "Rich Text" - and you will then be in HTML mode.

If you enter rich text, in HTML mode, and the rich text includes HTML keywords and symbols, you will have broken HTML - and the "Save" button will be inoperative. And, you will have a "broken" Text gadget. This is one of several possible causes of problems seen when adding / updating the HTML / JavaScript / Text gadgets.

>> Top

Saturday, 12 October 2013

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