Skip to main content

Reset A Gadget Or Post, By Toggling Edit Mode

Sometimes, a problem with a specific gadget or post, when displayed, can affect the appearance of the entire blog.

We've known for years, about the mysterious dropped sidebar. Sometimes, we see similar problems, in other blog performance.
  • Gadgets missing.
  • Gadgets visible, but they don't work.
  • Gadgets visible in the desktop view - but not the mobile view (or, vice versa).
  • Posts that are unreadable - or worse, previously published posts, in that index page, that are unreadable.

Both the HTML / JavaScript gadget, and the page or post, can be edited either as code ("HTML"), and as displayed ("Compose" / "Rich Text"). If you spend a lot of time in "Compose" / "Rich Text" mode, when editing gadgets, pages and posts, you may not know about "HTML" mode - or its dangers.

When instructed to use "HTML" mode, to install a specific tweak, you may never know about one good rule to follow, when editing HTML / XML code.
If you don't know the purpose of a given HTML phrase or word, leave it alone.

HTML code, which may appear as gobbledegook to the untrained eye, contains no unnecessary characters. Even adding or removing a single space, in some places, may break a gadget, page, or post - or worse, the rest of the template, following the broken gadget, page, or post.

If you have a problem with the blog, in general, you may be advised to "Reset the post template" - or maybe "Reset the gadgets". If you have a problem with a specific gadget, page, or post, you'll use a different technique.

Sometimes, when you use "HTML" mode in gadget, page, or post editor, and you break a gadget, page, or post, you can repair the broken gadget, page, or post by toggling between modes.
  1. Prepare the gadget, page, or post.
  2. Toggle from the current mode to the other mode.
  3. Toggle back to the "current" mode.
  4. If you need to finish the problem reset, in the "other" mode, toggle to that mode.
  5. Complete the reset.
    • If you're using the gadget editor, save the gadget.
    • If you're using page or post editor, re publish the page or post.
Inspect the blog. View different pages or posts, carefully. If no immediate improvement is visible, you may need to clear cache, and restart the browser. And try to be more careful, the next time you use HTML mode.

If this procedure does not work completely, you may have to next remove all formatting, if you're editing a page or post.

And when you're done repairing your mistake, backup the template. The next time you make a mistake, you may be using the Template Editor - and a template backup could save your sanity.

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.