Blogger Magic - Third Party Templates

There are millions of Blogger blog owners - and each owner has their own idea, how their blog should look.

Not every blog owner is willing to settle for using a Blogger supplied template. Some blog owners design their own templates - and others choose templates provided by non Blogger developers.

Some blog owners - even those with no technical background - choose third party supplied templates, and demand instructions in Blogger Help Forum: Learn More About Blogger. Not every blog owner can be supported, according to their personal level of need.

It's OK for you to install a new third party template, for your blog - though you should plan to do some extra work.

Third party templates should include some installation instructions.

A template publisher should provide instructions for uploading and installing their template. Installation procedures may vary, however.

• Scripted install.
• "Theme" Restore.
• "Theme" "Edit HTML".

Scripted install.

If the template publisher is honourable, using an install script, provided by the template publisher, can be the most reliable install procedure. A well written script can extract the template of your choice from the publishers library, copy it to your blog, and tweak the install to your satisfaction.

You do nothing other than select the template, and maybe some key options - and provide access to the dashboard. The script does all of the work.

This is similar to the selections on the Blogger dashboard "Theme" page - you simply select the template that interests you, and the script does the rest.

Giving control of your Blogger account, to an unknown third party, is not always the best idea, however.

Theme Restore.

If the template publisher provides a template as an XML file, and describes the template as "for Blogger", you can install the template from the dashboard. You will first download the template of your choice, to a local computer.

With a template downloaded locally, you use the Blogger "Backup / Restore" wizard, in the dashboard Theme page.

Start with the dashboard Theme page.

Hit the "Backup / Restore" button.

Hit the "Choose File" button.

Now, you have the file manager, provided with your computer. Select the file, containing the template just downloaded.



The "Backup / Restore" wizard is part of the Blogger dashboard. The template will be selected, using the file manager wizard on the computer being used.

Theme "Edit HTML".

This is the most universal procedure - if the template is provided as HTML. Just use the Blogger "Edit HTML" wizard, in the dashboard Template page.

The simplest install uses "Edit HTML", from the dashboard Template page.

Copy the HTML or Text file content, into the window.



In some cases, you may have to do some work, to use an HTML template.

It's your blog - and the template choice is yours too.

You can use any acceptable third party blog template. Many blog features will perform best, though, if you use the Blogger supplied post template.

To ensure up to date Blogger code, always refresh the post template, after installing a third party blog template.

And as always, I'll suggest that you backup the template, before and after installing a custom template.

If you install a third party template, you may have to support your blog on your own.

Please understand that Blogger won't be able to support your third party template - that is the responsibility of the template publisher. Problems with your blog, after installing third party accessories, may be yours to resolve.

Try and choose a reliable template, from a publisher with a past - and future.

The shinier and more feature rich your template needs are, the more carefully you should choose your template publisher. Even if the template that you choose works today, will it work next month?

When Blogger adds a new feature, next week, you can bet that they won't test their changes against the third party template that you're using. And even if your chosen template publisher is careful to test any Blogger changes, their testing won't start until Blogger makes their changes public.

And any problems that they discover will be yours to deal with, until a solution is developed and tested - and you install the corrected template.

If you choose a template made by a startup publisher, and you're their first / only customer, they may get a new day job, next month. The next time Blogger makes a change that requires an update to your template, they may not answer your plea for help.

With no support, you'll be left with one solution - revert your blog to a standard Blogger supplied and tested template.

---

There are millions of #Blogger blog owners - and each owner is different. Blog design - and templates used - will vary similarly.

Some blog owners cannot be satisfied by the Blogger supplied template library - and require third party produced templates.

Atom Vs RSS - Choose One, Using FeedBurner

Occasionally, we see a blog owner in Blogger Help Forum: Learn More About Blogger, asking about newsfeed formats.

Which is better, for my readers - Atom or RSS? How do I choose, what to provide, in my blog?

The competing newsfeed formats - Atom and RSS - have been a part of Internet life, for many years. Both formats have their devotees - and this is why there are two formats.

Both formats have their own advantages - and disadvantages.

You can change the URL of a FeedBurner source feed, to select Atom or RSS feed formats, from your blog.

You can use FeedBurner, or edit the blog template, to select a feed format.

Use the FeedBurner "Edit Feed Details" wizard, if you redirect your blog feed to FeedBurner.

If you don't use FeedBurner, you can edit the blog template, and manually change feed URLs. Note this will involve editing the post template, to change some links in the blog. This is not a recommended solution.

You may choose from 5 blog posts feed URLs, provided by this blog. You can do the same, with your blog.

• Atom (classic): http://blogging.nitecruzr.net/atom.xml
• RSS (classic): http://blogging.nitecruzr.net/rss.xml
• Atom (autodiscovery default, new): http://blogging.nitecruzr.net/feeds/posts/default
• Atom (new): http://blogging.nitecruzr.net/feeds/posts/default?alt=atom
• RSS (new): http://blogging.nitecruzr.net/feeds/posts/default?alt=rss

Do you really want to select Atom or RSS this way?

FeedBurner has two services, that let you mix and match Atom vs RSS.

• SmartFeed dynamically serves the right choice - Atom vs RSS.
• Convert Format Burner lets you statically select one format, or another.

Using either service, FeedBurner selects the desired feed format for you - regardless which Original Feed URL you provide, in "Edit Feed Details". Just give FeedBurner the default feed URL for your blog " ... /feeds/posts/default" - and let FeedBurner do the work, depending upon the service that you select.

You activate either service from the FeedBurner dashboard "Optimize" tab. Note that you should choose only one service, for each FeedBurner feed provided.

Important: We recommend not using this service if you use SmartFeed. SmartFeed will override any Convert Format settings in order to make your feed compatible with all feed readers, whether they support Atom, RSS, or both.

"SmartFeed" selects the best format, dynamically.

For the best experience by all readers, SmartFeed will automatically provide the feed format favoured by any feed reader used - as each reader views your feed.

Translates your feed on-the-fly into a format (RSS or Atom) compatible with your visitors' feed reader application.

Enable SmartFeed - and let FeedBurner choose the best format, for each different feed reader being used.



"Convert Format Burner" lets you choose the format - and version.

If the choice of feed format (Atom, RSS) - and even choice of format version (Atom 0.3, Atom 1.0, RSS 1.0, RSS 2.0) - matters to you, you can use Convert Format Burner, and select a specific format and version.

Nine flavors of RSS and now two formats of Atom ... who has time to keep track of it all? FeedBurner does! Let us convert your feed to any of the format choices listed below.

Enable Convert Format Burner - and you choose what feed format and version gets served, to all feed readers.



You can have multiple feeds, and multiple FeedBurner outputs.

If you have conflicting requirements, you can always setup multiple different FeedBurner feeds - and use different feed service options, for different feeds. You can then provide each feed in a consistent display, using the "BrowserFriendly" service.

---

If you want to serve the right newsfeed format from a #Blogger blog, you can either tweak the code in the blog template - or you can use a #FeedBurner feed, and activate the "SmartFeed" or "Format Burner" service. Using FeedBurner is a simpler choice, than the template editor.

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.

Diagnose Problems, With Blogs Using Dynamic Templates, Using Non Dynamic Templates

The process of examining browser source listings for a blog, and of having a blog owner carefully examine blog template code, is an important part of diagnosing many Blogger problems.

With blogs published to dynamic templates, neither source listings, nor template "Edit HTML", contain as much useful information, as with blogs published to non dynamic templates. Dynamic templates reference scripts, that are hosted in external libraries - and that cannot be updated or viewed.

The idea of having templates that were less customisable was originally supposed to encourage people to work on post content, and increase stability of their blogs - not create instability.

One of the original reasons for having the dynamic templates was to have templates that would encourage blog owners to work more on content - and less on style.

Dynamic templates were designed for less customisation - and increased reliability.

Having the less customised templates would, hopefully, have made the dynamic templates more reliable. Unfortunately, Blogger chose to add features to the dynamic templates, to make them more popular.

The "infinite scrolling" feature of the dynamic templates impressed people, who decided that "infinite scrolling" would be useful for their blogs - but without having noted that dynamic templates have less options for customisation.

People, who like the existing dynamic templates features, demand more features for them. And, they cause more problems, for themselves - since many of them lack the ability to diagnose their own problems.

Eliminate general blog problems, by re publishing to a non dynamic template.

Any time a blog problem is diagnosed, and the problem involves a blog that uses a dynamic template, it's a good idea to start by re publishing the blog to a non dynamic template. Try to diagnose and eliminate any general blog problems, before tackling problems caused by tweaking of dynamic templates.

Just go to the dashboard Template wizard, and choose any non dynamic template - then "Apply to blog". Then, reset the post template (if the posts are involved, in the problem).

Publishing to a non dynamic template lets us use standard diagnostic tools.

With the blog published to a non dynamic template, you (the blog owner) can use the Template Editor to examine general (non dynamic) template CSS, HTML, and / or XML code. Also, you (and any helpers) can use a browser "View Source" window, to examine the rendered blog code.

If you diagnose a problem with non dynamic code, you can edit and correct any problems found. Once that is done, and you are satisfied that there are no non dynamic template related problems, re publish the blog to a dynamic template - and diagnose any remaining problems.

As always, template backups are strongly advised.

If you decide to make any changes to the template code, as always, I advise that you backup the template - before and after making changes. Whenever you detect a problem, recover the template to the backup taken before the changes, and see if this fixes the problem noted.

Publishing A Gadget To A Specific Page

Long before Blogger developed static pages, blog owners had wanted to have some accessories or gadgets visible only on specific pages.

Initially, we discovered that gadgets could be displayed conditionally, based upon the URL being displayed. This is a fairly simple task, when you get used to it - but it requires editing the template HTML - and can look a bit scary, to those inexperienced in template editing.

Recently, we realised that some gadgets can be embedded in a page or post, by editing in HTML mode - and accomplish the same. I demonstrated my custom "Contact Me" gadget, using that ability.

Both the technique of embedding a gadget in a page or post - and of conditionally displaying a gadget - have their advantages, and their disadvantages.

Embed A Gadget In A Page Or Post

My custom "Contact Me" gadget, which is provided by Google Docs as an IFrame embedded page, is published in my static page "Contact Me, Improved".

<iframe src="https://docs.google.com/forms/d/1JvoY2yf5aTChnvXlCgGsUerSCtI7RHpRdkq5SPBPm90/viewform?embedded=true" width="700" height="800" frameborder="0" marginheight="0" marginwidth="0">Loading...</iframe>

That's the code for my gadget - you can make your own, in 10 - 15 minutes. You can use this technique with any Google Docs based file.

My expanded Followers gadget is part of my static page, "Followers". The code for that page was provided by Google Friend Connect, and is no longer available. You may now install the "Followers" / "Google Friend Connect" gadget, using "Add a Gadget".

The Followers gadget is JavaScript based, though - and the rendered gadget code can be extracted from the blog source, using any suitable text based browser. Having extracted the JavaScript, it can be added to any page or post, in HTML mode, just as I did to make "Contact Me, Improved".

Display A Gadget, Conditionally

Gadgets which are provided as XML, and do not provide convenient rendered JavaScript code, cannot be easily embedded in a page or post. These gadgets will still be added using "Add a Gadget", and will require the conditional template tweak. My Labels index page, "Topics", is an example of this technique.

Any BlogList or LinkList gadget can be found as rendered HTML, and the code can be extracted - again, from a blog source listing - but both bloglists and linklists are dynamic - and frequently long. If you extract the rendered source, you get a static copy - - which is fine, if you never plan to change your list.

The blog has half a dozen lists, of various types - and I like to add or remove list elements, whenever necessary. I enjoy the Quick Edit feature of the "Peer Resources" bloglist, for instance - and have no intention of publishing that bloglist as a static HTML based linklist. If I was to display "Peer Resources" on a specific static page, I would use the earlier technique of editing the template XML code, and adding a conditional.

It seems as if it should be possible to add XML code, directly, into a page or post. If I discover the appropriate technique for doing that, I will surely update this post.

Know The Alternatives

Just know the alternatives, and choose wisely.

Tweak The Post Template, Only When Necessary

Occasionally, we see the query, in Blogger Help Forum: How Do I?

How do I change these captions? / Add this feature? / Remove specific components of this feature?

Conversely, we see in Blogger Help Forum: Something Is Broken

Why does this new Blogger feature not work in my blog?

These questions, in many cases, may be related. We can see the connection, when we look closer at how the changes are applied.

Many changes to our blogs, that are part of the comments / posts / post header / footer, are made in the post template.

The post template is an unobtrusive section in the blog template, that lets us change the blog template as we wish - while allowing Blogger to update the comments and posts code, as they add new features, or update existing features.

Blogger lets us change the post template, using "Configure Blog Posts".

Blogger provides the "Configure Blog Posts" wizard - and lets us change specific features in the post template.

The options in "Configure Blog Posts" do not satisfy everybody - and here is where many problems start. Some blog owners want features or selections that are not provided by "Configure Blog Posts" - but are part of the post template.

Some features have to be installed as post template tweaks.

To install these features, the blog owner uses the Template Editor, and tweaks the "Blog1" template widget.

Once the post template is tweaked, by the blog owner, the blog has a non standard post template. When Blogger applies their next post template update, to install or update a Blogger supplied feature, against a blog with a non standard post template, they have 3 options.

1. Overlay the entire post template, with their updated post template. The blog owner sees all tweaks previously made, suddenly vanish. Some of the owner applied features simply disappear, others stop working - with no explanation or warning.
2. Overlay specific portions of the post template, with their updated post template changes. The blog owner sees some tweaks previously made, suddenly vanish. Some of the owner applied features simply disappear, others stop working - with no explanation or warning.
3. Not install the updated post template. The new Blogger feature doesn't work - and the blog owner is left complaining about broken Blogger updates, while other blog owners are enjoying the new feature.

When Blogger upgrades the post template, what happens to your tweaks?

If Blogger updates the post template, and some owner applied features disappear or stop working, the blog owner can simply install the necessary tweaks, again. Having kept the notes, or code snippets, from the original install, many blog owners simply install everything again.

Unfortunately, if the Blogger post template changes were applied in the same post template section as the owner applied tweaks, the owner retained notes or code snippets may be out of date - and installing them again may break one or more Blogger supplied features.

Some post template tweaks can have effects outside the post template.

Some owner applied changes, if installed improperly, can affect other sections of the template, in general - and cause mysteries such as problems updating accessory gadgets, and problems using the Template Designer.

The end result is that owner installed post template tweaks must be made, selectively - and any Blogger changes, publicised or non publicised, may necessitate re install of any owner applied tweaks. Owner applied tweaks must be re installed, character by character - and frequently with the readers complaining about an unexpected change or broken blog.

The post template is actually another example of "well enough", for many blog owners.

---

Tweak The Post Template, When Necessary - And Only, When Necessary

The Layout Template "Edit HTML" Wizard And "Expand Widget Templates"

Sometimes, when we're working on a problem that requires editing the HTML in a layout template, we need to understand the need to expand (or not expand) the widget templates. This month, for instance, we have hundreds of blogs containing malicious code, unknowingly installed by the blog owners. The malicious code must be removed, but the installed code aggressively prevents use of the "Page Elements" wizard, and the "Remove" button.

---

Note: The selection to "Expand Widget Templates" has been replaced, by folded lines of code, which are now expanded selectively.

---

When the "Page Elements" wizard can't be used to remove code, you have to use the "Edit HTML" wizard, and remove the individual gadget entries, one by one.

Here's what the unexpanded line entry for one problem gadget looks like

<div class='widget Gadget' id='Gadget1' />

That's easy enough to find - and to delete.

Here's what that entry looks like, expanded. To examine, and maybe modify, the gadget code, you have to select "Expand Widget Templates". To simply remove an entire gadget, on the other hand, do not select "Expand Widget Templates".

<div class='widget Gadget' id='Gadget1'>
<h2 class='title'>Maukie - the virtual cat</h2>

<div class='widget-content'>
<script type="text/javascript">
if (!window.gadgets || !gadgets.rpc) {
document.write('<script type="text/javascript"' +


'src="http://www.gmodules.com/gadgets/js/rpc.js?v\x3d9261b340ef5af1e5faca55914670c7\x26container\x3dblogger\x26debug\x3d0\x26c\x3d1">' 

+
'</scr' + 'ipt>');
}
</script>

...


</span>
</span>
<div class='clear'></div>
</div>

OK, the example above was heavily excerpted. If I was to include the entire code set for this one gadget, I would risk this post (my main page display) being subject to segmentation, caused by Auto Pagination. So, I gutted 95% of the interior code. But, you should get the idea.

The point is, when you need to remove malicious code, do not select "Expand Widget Templates". Then, find (as an example)

<div class='widget Gadget' id='Gadget1' />

and delete that one line.

Problem solved.

And next time, be more selective what gadgets you install in your blog.

>> Top

Editing The Blog Template

The template is like the skeleton of your body - you can't see it (easily), but the success of the blog depends upon its being there, and being structured properly.

If you're going to have a blog, and publish it effectively, eventually the dashboard Layout and the Template Designer pages won't do enough for you. You're going to want to get to the details, underneath the GUI processes.

You access the template editor using the dashboard Theme page, where you will find (among other options) the "Edit HTML" button.

Click on "Edit HTML".



Clicking on "Edit HTML", you may get a serious warning to read.

Directly editing HTML may affect the way some features work and is only recommended for advanced users. Editing template HTML may unpredictably affect other Blogger features. We recommend using the Template Designer first, where you can Add CSS under the Advanced section.

Should you choose to click on "Proceed", you'll be into the "Edit HTML" display.

Edit carefully. Some changes may require editing / removing multiple lines of code.



With a Classic template, you have just one major activity when you're in "Edit HTML" - and that's what the name suggests, you edit the HTML. You'll have some CSS code, but no XML - so it's all relatively straightforward.

With a Layout template, you'll have a few extra options.

• Backup ("Download a copy") the template.
• Upload the template ("Backup / Restore").
• Revert widget templates to default.
• Revert to classic templates.
• View classic template. If you started the blog with a classic template, and upgraded to layout, you can look here to find any left behind HTML accessories and tweaks. You can add as "HTML / JavaScript" gadgets, any well defined accessories and tweaks.

With a Designer template, you'll have one additional minor option.

• Revert the template to Layout.

And with a layout template, you'll have "Edit HTML", but with a few more tweaks than with a classic template. You'll have CSS and HTML - and XML - code to edit. And don't overlook the possibility of using HTML code in place of XML code, in a layout template.

One of the least understood selections in the Template "Edit HTML" wizard is the option to "Expand Widget Templates" , which has been replaced by selectively unfolding any gadget to be edited. Just understand when to unfold - and when to not unfold.

Remember that Blogger blogs offer many possibilities. Some code can be installed using HTML / JavaScript gadgets, as an alternative to adding code to the template using "Edit HTML".

And please, as always - backup the template, before and after using Template Editor.

Duplicate Blog Posts? Remove The Duplicate!

As a savvy consumer, you likely love to hear about offers for 2 for the price of 1, of something that you buy frequently. That's a great deal, normally.

It's not for blog posts, though.

When you start to see double in your blog, chances are that you duplicated the Blog Posts entry in the template. It's not hard to fix, fortunately.

Edit the blog template, using the dashboard Template - "Edit HTML" wizard. Do not expand or unfold any widgets.

If you unfold either 'Blog1' or 'Blog2', you will have to find the end of the unfolded gadget section, which could be hundreds of lines later. If you delete 1 too many, or 1 too few, unfolded lines, you will get a syntax error.

Error parsing XML: ... The element type "b:section" ...

Deleting just one line (see below) is way easier, believe me.

Look for two lines, in the Body of the template, which may or may not be immediately next to each other in sequence:

<b:widget id='Blog1' locked='true' title='Blog Posts' type='Blog'/>

...

<b:widget id='Blog2' locked='true' title='Blog Posts' type='Blog'/>

Remove:

<b:widget id='Blog2' locked='true' title='Blog Posts' type='Blog'/>

Leaving:

<b:widget id='Blog1' locked='true' title='Blog Posts' type='Blog'/>

Save the change. You will get a stern warning when you save, demanding that you confirm that you really want to delete "Blog2". Obviously, you do. And don't forget to clear browser cache, and restart the browser, to reliably test your change.

Remember to save a copy of the template, before and after doing this.

And now, since you're here, and if you just removed a duplicate post template from your blog, help me to help others, and think why you're here.

• What changes have you made, to the blog?
• What accessories have you installed?
• Any templates - Blogger or third party? - installed?
• Any changes between classic and layout templates?
• What Blogger features / wizards do you use?
  • Draft Blogger?
  • New, or Old, Post Editor?
• What third party services have you ever allowed to access the blog directly, to install something?

Solving this problem starts with you.

>> Top

The Two Templates

Your Blogger blog uses two different yet related HTML / XML templates, in formatting and displaying your posts.

The blog template defines objects that are consistent for the entire blog - and the post template defines objects that are consistent for each post (though the content of each post will vary, from post to post). You can change the blog tempate, when you wish.

The post template, when the blog is published, becomes part of the blog template - but the two are maintained separately. This lets you change your blog template (and the page layout) without affecting the post template (and the posts layout), and vice versa. When Blogger makes changes to post related features, they change post template code.

The blog template is configured using the dashboard Layout and Template pages.

The blog template is configured using the dashboard Layout page - or the Template - "Edit HTML" Template Editor.

You can add / arrange objects on the page, and re locate any object that you want, anywhere on the page (with a few exceptions), using a GUI drag and drop process. Wherever you drag it, the object becomes part of the page, and displays in that location on the page. And when the page is displayed, the object in question is displayed there, with one copy of each object / page.

When there are problems with any of the blog content except the posts themselves, and the problem can't be resolved by editing a widget or using the Layout "Edit HTML" wizard, the blog template is possibly corrupt - or probably just out of date.

Third party developers don't have access to the latest Blogger post template code. If you install a third party template, you frequently get out of date post template code - and broken comment / post features.

A corrupt / out of date blog template is, most easily, resolved by getting a new template.

When you have a corrupt blog template, if you didn't back the template up previously, you'll have to use the "Pick New Template" wizard, and get a fresh copy of your template. Or copy it and paste it into the "Edit HTML" window. Note that each widget includes a quickedit function (the "screwdriver / wrench" icon), which is also part of the blog template.

The post template is configured using "Configure Blog Posts".

The posts template is configured using the "Configure Blog Posts" widget in the dashboard Layout wizard. You can arrange (but can't add) objects using the GUI blog posts widget. If you want to add an object to be part of the posts, and display with each post, you either add it into each post manually, or using the (Settings - "Posts and comments") Post Template "Edit" link.

The Post Template Editor (please, do not confuse this with the "Template Editor") uses HTML code, not GUI - and it works for new posts only.

When there are problems with the posts, and the problems can't be resolved by editing the posts using the post editor, the post template is possibly corrupt. This can sometimes result from unwisely applied tweaks, made by the blog owner.

A corrupt post template is resolved by refreshing "Blog1", using Template Editor.

When you have a corrupt / out of date post template, you have to refresh the post template. This requires that you reset gadget "Blog1", in the Template Editor.

Any time you install a third party template, you should refresh the post template. Third party template developers have their own product development schedules - and will not reliably have access to the latest version of the post template.

Note that the post template also includes the post quick edit function (the "pencil" icon), the comments, and the labels - all elements which are different for each post.

Be sure to backup the template, before and after refreshing the post template.