Inaccessible Comments, On Some Popular Posts

Viewing comments, on some popular blogs, one may get the idea that not as many comments are being published, as are immediately visible.

With a large comment complement, comments are paginated - with some comments hidden behind a link, captioned "Load more". The "Load more" link is JavaScript based - and there is a problem.

The "Load more" link does not always work, on all blogs.

Comments on some blogs may be unreadable - with the "Load more" link not operational.

Some posts never display all comments.

Look at the bottom of the page, below the post.

And there is the "Load more" link.

And the link, as seen when one mouse over it, is shown to be JavaScript based.

And clicking on the link yields the caption "Loading ...".

And "Loading ..." never goes away - and we get no view of the missing comments.



I've seen this problem with blogs using both dynamic and non dynamic templates.

Both dynamic templates, and non dynamic templates, appear to use comments paginated behind "Load more" - and may exhibit this problem. I've seen this problem, reported in Blogger Help Forum: Get Help with an Issue, for both template types.

I have reproduced this problem, using two blogs.

Here are two recently reported cases, reproduced in my testing today. I do not know how long both cases may be active.

http://slifkinchallenge.blogspot.com/2016/05/thank-you-yehoshua-duker-and-yosef.html
https://productforums.google.com/d/topic/blogger/RotUfv8AwuU/discussion

http://istanbulkonstantinopel.blogspot.com/2014/03/study-in-turkey-2.html
https://productforums.google.com/d/topic/blogger/7Yau3KKR9mo/discussion

Noting that both blogs are (natively) published in countries that are subject to local country codes (Israel and Turkey, respectively), I will deny that to be a simple affinity - since I viewed both blogs from my browser, as "blogspot.com", as I reproduced the problem. That said, that is an interesting coincidence, no?

There are several possible causes of this problem. Adding the above observation, some of these causes may be more or less relevant.

• Comments feed setting.
• Comment feed content / corruption.
• Cookie / script filters.
• HTTPS Redirect.
• Occam's Razor.
• Post template corruption.

Comments feed setting.

Features like the comment reply option, and blogs published to dynamic templates, require a full comment feed. It's possible that comment pagination, behind JavaScript links, is similarly sensitive to the comments feed setting.

This detail will affect everybody - both blog owner(s) and reader(s) alike. And it will probably affect all posts, uniformly.

The solution for this problem would involve checking - and correcting - the comments and feed settings, for the blogs involved.

Comment feed content / corruption.

Similar to the problem with the Blogger blog post published location, it's possible that some unknown detail in the data could interfere with script functionality.

If the problem involves content in one post - or a comment on one post, it's possible that comments for one post could be affected; but other posts could paginate comments successfully.

This detail would probably affect everybody, uniformly.

The solution for this problem will require determining what feed content detail causes the problem. This will probably involve affinity diagnosis.

Cookie / script filters.

Any problem which involves a JavaScript based link, both cookies and scripts are always going to be involved. Any filter that interferes with either cookies (identity) or scripts (link functionality) will always be a possibility.

Filters may affect either blog owners and / or blog readers, uniquely. A problem that involves some owners / readers will likely involve filters.

Thanks to the effect of country local domains, cookie / script filters may affect individuals geographically.

The solution for this problem is to check / open up script filters - and then check / open up cookie filters.

HTTPS Redirect.

Both blogs, identified above, appear to not be using the "HTTPS Redirect" option. It's not impossible that this is another feature, broken by the SSL Rollout.

Occam's Razor.

Considering the most simple alternative, is it possible that paginated comments are simply inoperative? Maybe, because of (or incidentally involving) the SSL Rollout??

Post template corruption.

Comments are part of the post template. It's likely that proper comment functionality also requires a clean post template. This detail will probably affect everybody - though it's possible that there could be code that is sensitive to some owners / readers, but not others.

The solution for this problem is to reset the post template, on the blogs involved.

The bottom line.

This problem, if not incidentally solved by a Blogger code change, will probably not be diagnosed, immediately.

More examples of this symptom are badly needed. Right now, we have seen only a handful of people with blogs that are popular - and generate comments in sufficient volume - and have reported this problem.

---

Some #Blogger blog owners, who publish blogs with posts that receive large volumes of comments, report inability to display all comments published. Comments, when displayed in large volumes, are paginated behind JavaScript based links - and some links, when clicked, don't seem to work.

https://productforums.google.com/d/topic/blogger/7Yau3KKR9mo/discussion
https://productforums.google.com/d/topic/blogger/RotUfv8AwuU/discussion

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.

Post Data Cannot Be Moved Above The Post Body

Blog owners have been requesting the ability to position various post content items above the post body, for years.

We've seen reports, in Blogger Help Forum: Get Help with an Issue, about problems moving Comments, Labels, Share Bar, and others.

Several years, "Arrange Items" was upgraded to allow Labels to be moved above the post body. That option was provided briefly - then removed later.

Depending upon what items are currently in a specific location, moving other items into - or out of - that location may or may not be successful.

The "Arrange Items" wizard is not magical.

Code for each item, which can be moved, has to specifically support repositioning into any one of the target boxes.



Any item move may, or may not, be successful. Various details may affect success.

• Item being moved.
• Item current location.
• Item target location.
• Other items in the same current location.
• Other items in the same target location.
• Post template status - customisation, etc.

Frequently, when a problem with "Arrange Items" is reported, the blog owner is trying to target a position above the post body.

Diagnosing a post template problem, which involves arranging items, can involve any of these details. Not so many blog owners want to re arrange items - and even less want to arrange items above the post body - so there is not a lot of experience with diagnosing these problems.

Success - or failure - may involve several scenarios.

In some cases, the drag and drop operation, in "Arrange Items", may not accomplish anything. The owner may drag the item into place - and watch as the item perversely moves itself back, to where it was.

In other cases, the move may appear successful. The item may seem to move, and stay where is is dropped.

The owner may Save - then refresh blog display, and see the item still where it was. Opening "Configure Blog Posts", the item may or may not be displayed where it is now - or where it is wanted.

In some cases, the item may be moved successfully - and some other item, in the original or current location, may stop working.

We have seen all of these problems reported. Frequently, there is only one course of action.

• Reset the post template.
• Start over.

In many cases, resetting the post template is the only way to repair a problem caused by moving an item to where it should not go. With the template reset, the owner will have to choose whether to try again - and risk a repeat, of the same problem.

---

Moving #Blogger post template items, from one location to another, is not always successful - and sometimes causes problems with other blog content. Attempting to move items above the post body is a frequent cause of problems.


https://productforums.google.com/forum/#!topic/blogger/Gv2Mgnpg3TE

https://productforums.google.com/forum/#!topic/blogger/u6mZEd1mjLY

https://productforums.google.com/d/topic/blogger/u6mZEd1mjLY/discussion

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.

Don't Try To Number Dynamic Pages

One interesting question, which we see occasionally in Blogger Help Forum: Learn More About Blogger, would be about making the blog easier to read - if the blog were static.

How do I number the pages, in the blog?

This blog owner does not quite understand the concept of dynamic content.

With a static website, and each page linked linearly, one after the other, it might make sense to number the pages.

Blogger blog content is dynamic.

A Blogger blog has dynamic content. Each reader retrieves the posts, in reverse date sequence, in a number of contexts.

• In main page view, one page linked to the next - owner selectable maximum posts / page, auto paginated.
• In individual post view, one post linked to the next - one post / page.
• In an archive retrieval, one page linked to the next - a maximum of 20 posts / page, auto paginated.
• In a label search, one page linked to the next - a maximum of 20 posts / page, auto paginated.

Each label in the blog can generate a different label search, one search / label.

We say that the content is dynamic, because each of the above contexts use blog content, retrieved just when a reader clicks on a link.

Each time content is retrieved, for each reader, it will differ.

Each different retrieval will generate a series of physical pages of display, with a different combination of posts. Each retrieval will be paginated according to amount of content, by auto pagination.

If the posts are summarised using Jump Break, pagination will reflect the visible post content. With other "Read More" solutions, this may or may not be the case.

Dynamic indexes can use any combination of various dynamic accessories.

You can index the posts in a blog, using various dynamic sidebar gadgets.

• An archive index.
• A label index.
• Any number of linklists.
• Any number of feed gadgets.

Again, each index will be dynamic.For truly dynamic indexing, you can provide a single blog search - or a multiple blog search - or even a label combination search.

You can get installable gadgets, and custom templates, from various third party developers. Some gadgets and templates will let you setup an index (whether dynamic, or static), with page numbers. This will be third party code - and carries with it the risks of using third party code.

Non dynamic accessories require post template tweaks.

Non dynamic indexes generally install as code, inserted into the post template. The post template is not a blog component that should be tweaked, without understanding the risks.

Also, if you apply to host AdSense ads on the blog, you'll probably get a refusal, cited as "Difficult navigation". The AdSense crawler can't navigate JavaScript based links - and won't be able to analyse post content, to place ads.

The AdSense crawler can't navigate this blog, with numbered pages.



All of the above details affect how much content may appear on one physical page, and how many pages may be relevant to the retrieval. With these unknowns, it is not productive to identify each post - or set of posts - using page numbers.

How many index listings would you want to keep - especially considering that any one index could change, in the next minute, as a new post is published, or maybe a label is added to, or removed from, one or more posts?

Blogger content is dynamic. Treat it, dynamically.

Confusion From Blogs That Use Smart Links In Titles

Some blog owners like to publish blogs that use custom colours, in the titles.

Carefully coordinated colours are important, in some blogs. Both the blog title, and the individual post titles, in many blogs, are clickable link captions. The blog title links to the blog home page, and / or the post titles link to the individual post pages.

Some blog owners get confused, when they try to set the colour of the titles, to a custom colour - and see link colours (which vary according to status), instead of the selected custom colours.

With some templates, both the blog title, and the post titles, may be captions for "smart" links.

A "Smart Link" is clickable, only when it leads to a different page.

With a smart link, the caption is clickable only when you are viewing a page not targeted by the link. When the link is clickable, it becomes subject to the "link" vs "visited link" colour combination.

With a blog that uses a custom colour title, and links in the titles, you will have 4 possible title colours.

• Custom title colour.
• Link colour.
• Visited link colour.
• Hover colour.

The above colour settings are provided, for some templates, when one uses the Template Designer "Advanced" menu. All settings are not included on all templates - though you can add any needed setting, with a little work.

A post title is clickable, only when the post is viewed on an index page.

With a smart link, the title in question will be a link only when you are not viewing the page that's targeted by the link. The blog title smart link, for instance, will point to the blog home page - and each post title smart link will point to the individual post page.

• When you are viewing the blog home page, the blog title will not be clickable. Each post title will be clickable link captions.
• When you are viewing an individual post, the blog title will be a clickable link caption, and the post title will not be clickable.
• When you are viewing an archive retrieval or label search, both the blog title and posts titles will be clickable link captions.

It appears that the post title smart links are enabled, when the post permalink is part of the published date / time, in the post footer. This option was common, with older templates; with some (but not all) Layout and Designer templates, it may also be available.

If the post permalink is not provided in the post footer link, it appears that "smart" links may not be an option.

If you don't want the "smart link" colour action, you can add a CSS rule, and make page / post titles a consistent colour.

h3.post-title {
color:#000000;
}

This will, for instance, make all titles black. Be observant, though - and make sure that this works, consistently, for you!

The "Reply" Option, For Embedded Comments

The option provided some time ago, to the embedded comment form, to allow "threaded" comments, is becoming quite popular.

Unfortunately, the "Reply" link does not always work. Blog owners and readers alike complain.

I click on "Reply", and nothing happens!

This problem appears to have accelerated recently, possibly resulting from the hasty rollout of the new anonymous comments CAPTCHA - but there are other less obvious possibilities, too.

The threaded comments "Reply" feature, a seemingly minor addition to the Blogger code base, can have problems with a number of issues.

• A Full Blog Feed.
• An up to date post template,
• The Google "One account" login, and cookie filtering.
• The recent addition of the anonymous commenting CAPTCHA.
• The threaded comments script, and recent script filter updates.

A Full blog feed is required.

Many blog owners are not aware that the "Reply" option won't be available, without a Full Blog Feed. Go to the dashboard, and look at "Allow Blog Feed", under Settings - Other - Site feed.

For threaded comments, you will need a Full Blog Feed (for both comments and posts) - and this will exclude private blogs.

Any "Allow Blog Feed" selection, other than "Full", will be a problem.



An up to date post template is a good idea.

Threaded comments, like every other post and comment feature, works best on an up to date post template. Any time threaded comments stops working, and you have not changed the blog feed, try resetting the post template. Now, here's hoping that you have not made extensive post template tweaks.

The identity of the person who wants to reply is useful.

Threaded Blogger hosted comments code, like threaded Google+ hosted comments, other commenting scripts, and many other Blogger features, needs access to the login cookie, to identify the person preparing to comment. Because of the use of the Google "One account" login, "third party" cookie filters must be examined.

Anything that interferes with the CAPTCHA will be a problem.

The recent addition of the anonymous comment CAPTCHA, appears to have caused some problems. This may be an matter for Blogger Engineering to correct.

Anything that interferes with scripts will be a big problem.

All Blogger scripts, including the script which services the "Reply" link, are subject to script filtering. Script filters are subject to update, on every different client computer - generally without notice to the computer owner. Always check script filters.

Blog owners and readers, alike, need to be aware of the issues, to use Blogger effectively. Threaded comments are no exception to this requirement.

Use "Quick Edit" To Bypass The Dashboard Menu

One very useful Blogger feature is the option to bypass the Blogger dashboard - to edit the various gadgets, and existing blog posts.

The feature, termed "Quick Edit", provides two different icons, generally visible to the proper recipients, with the option enabled, on the published blog.

• The "Quick Edit" "pencil" is visible to administrators and authors, in the posts toolbar, to the right of the "Email Post" icon. This will generally be in one of the post footer lines.
• The gadget "screwdriver / wrench" icon is visible to administrators, to the lower right of each template gadget (except for "Blog Posts").

Though the "screwdriver / wrench" icon is more visible, that icon has no name, and no selection option in the Blogger dashboard. And, there are more mysteries.

The "Quick Edit" option is selected using "Configure Blog Posts", as "Show Quick Editing".

Most blog owners enable "Quick Edit" on their blogs, routinely.


What I see, of the"Search Me, Direct" gadget, in this blog.


The Quick Edit icon, that I see. You should not not see the icon, when you view this blog - but you may see it, on a gadget in your blog, when you view your own blog.


You enable "Quick Edit" from the dashboard Layout page.
Though the option affects visibility of the "screwdriver / wrench" icons, in the blog template, there is no dashboard Settings selection. It is only selected as a post template option, in "Configure Blog Posts".

The "Configure Blog Posts" wizard is accessible only by Editing the "Blog Posts" gadget, from the dashboard Layout wizard. There is no "screwdriver / wrench" icon which allows access to the "Configure Blog Posts" wizard.

Names used to identify the "Quick Edit" icon may vary.
Adding to the mystique here, residents of Europe may term the "wrench" as a "spanner". Long ago, some blog owners referred to the "screwdriver / spanner / wrench" icon as "dragonflies".

Both the "pencil" and "screwdriver / wrench" icons may or may not be consistently visible. Both icons have been known to be invisible / non functional, with improperly configured cookie or script filters.

The icon may be visible, even when not operational.
And thanks to caching, a blog owner may see either the "pencil" or "screwdriver / wrench" icon when logged out of Blogger - and mistakenly conclude that the public, in general, is able to access the Dashboard or Post Editor for his blog, and change blog options or edit posts. Having logged out, then clicking on any visible icon - or clicking on a carefully configured link URL, we can verify that no illegal access is possible.

And some blog owners, thanks to an intriguing terminology variation, may refer to the "pencil" as an option for editing a "blog".

All that said, use of the Quick Edit URL - with Quick Edit enabled or not - can be very useful, in removing gadgets properly identified.

Blogger Magic - Hiding The Blog Pager And Blog Feed Subscription Lines

One of the neatest magic tricks is to make something disappear, with just a flick of the wrist (whether or not holding a "magic" wand).

We see occasional requests to make template components disappear. Many times, we end up recommending editing the blog template. Sometimes, unwanted components are part of the post template - and we have to explain why editing the post template is not a good idea.

Some template components, when properly identified, can be made to disappear with the proper CSS rule. CSS rules can be added, using the Template Designer - and do not require editing the template.

Even better news, CSS rules added using "Add CSS" are persistent. Even changing the blog template - or resetting the post template - does not erase CSS rules, added using the Template Designer.

Two post template components, regularly requested for removal, are the "Blog Pager" caption lines

Newer Posts   Home   Older Posts

and the "Post Feeds" caption

Subscribe to: Posts (Atom)

To hide these components, a simple one line CSS rule is necessary, added using the "Add CSS" option in the Template Designer.

For the "Blog Pager" line:

#blog-pager {display:none}

For the "Posts Feeds" line:

#post-feeds {display:none}

As with any addition using "Add CSS" always precede and follow any added rule, with a blank line.

This trick, as with many magic tricks, is easier to do, than to explain. Was I to add this to my blog, I would have been done, long ago.

>> Top

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

Loss Of Ability To Let The Reader Choose A Dynamic View Or Non Dynamic View, When Viewing The Blog

When the Blogger dynamic templates were first introduced, back in 2011, they provided choices.

Besides letting the reader choose, on the fly, which dynamic view to use, it was possible to let the reader choose whether to view the blog using a dynamic view - or a non dynamic view.

When dynamic templates were first introduced, they offered a dynamic view of the blog posts - and little else. Popular features like static pages were added later, and in pieces.

As the various pieces of the dynamic views became better defined, the need to switch between dynamic and non dynamic views became less essential - and eventually, some choices were eliminated.

If you look at the menu bar for this blog, you'll see a selection "DYNAMIC".

If you click on the "DYNAMIC" menu selection, you'll get a link to the "sidebar" dynamic view of this blog. At one time, this would have actually shown you this blog, using a dynamic template. Now, it leads you to a blank screen.

We asked Blogger Support recently, about the recently discovered inability to allow the reader to switch from a non dynamic view to a dynamic view, and were told that option had been discontinued, for "privacy reasons".

Apparently, some portions of the posts, when removed using the "Configure Blog Posts" wizard, were still displayed when a dynamic view was used. This caused problems for some blog owners, who had intentionally used a non dynamic view with personal details like author name removed from the posts. When they viewed the blog in a dynamic view, they found their name displayed, for all to see.

If anonymity is your concern, there are other techniques, which you may consider.

Another possible problem involved the blogs being simultaneously published using a dynamic template, and a non dynamic template. Last year, many blog owners reported various problems encountered, when their blogs were viewed using a dynamic template. It's possible that solution of the various problems involved simplification of code - including the ability to use either a dynamic or non dynamic view, at will.

Whatever the details, it appears that dynamic templates, and non dynamic templates, are completely separate options now. And as Blogger improves the dynamic templates in general, this should be good for all blogs.

>> Top

The New GUI Template Editor, And Removing The "Blog Posts" Gadget

Since the most important part of almost all Blogger blogs is the posts, the "Blog Posts" gadget is an essential element in the template. Sometimes we have to remove the gadget though - maybe the gadget is corrupt - or in odd cases, we may have a duplicate "Blog Posts" gadget.

In either case, the solution is known, and is quite simple.

Remove (the / one) "Blog Posts" gadget.

Unfortunately, not everybody, needing such advice, is able to do this. People using the Template Editor in the New Blogger GUI (2011) may find, to their frustration, that removal of a "Blog Posts" gadget isn't permitted.

Sometimes, when we advise someone to remove a "Blog Posts" gadget, we find the advice not well received.

It won't let me do that!

or

I get a bX code, when I try to save the change!

Apparently, somebody who designed the New GUI Template Editor decided that removing "Blog Posts" just isn't a necessary option.

Right now, if you're going to remove "Blog Posts", you have to switch back to the Classic GUI.

>> Top

Two Level Comments, And One Known Post Template Update

From feedback being received about the recent release of two level commenting, and the many different problems attributed to the release, it appears that there is one commonly identified update to the post template. It's possible that adding this one change, to some blogs with tweaked post templates, may eliminate the need for a post template refresh.

This is a simple change - but it must be made in 4 different places. I highly recommend that you backup the template, before and after making this change. Allow 30 minutes, to concentrate properly on the task.

Installation of this one post template patch may eliminate the need for many people to refresh the post template. It's also possible that this change, done in reverse, may let you disable two level comments, should you wish. In either case, please do this carefully, when you are relaxed, and able to concentrate.

1. First, backup the template.
2. Edit the template using the "Edit HTML" wizard, and select "Expand Widget Templates".
3. Carefully search for each instance of
   

   <b:include data='post' name='comments'/>

4. Note that the target snippet (above) is entirely contained in the replace snippet (below). When you identify each snippet found, carefully examine it to make sure that the required code is not already present! Do not replace the target snippet with itself, redundantly!
5. Replace each instance found, if not already present, with
   

   <b:if cond='data:post.showThreadedComments'>
     <b:include data='post' name='threaded_comments'/>
   <b:else/>
     <b:include data='post' name='comments'/>
   </b:if>

6. Save Template.
7. Clear browser cache, and restart the browser. Test your changes.
8. Again, backup the template.

Again, I'll advise you to backup the template, before and after doing this.

>> Top

Blogger Magic - A Static Home Page

Every week, somebody asks for such a simple blog feature.

How do I have a single blog post always displayed, for the home page?

There are many things that Blogger has yet to provide, and this is one. A blog, by definition, contains a dynamic home page, with the most current posts displayed.

Today (sorry, too late!), if you view this blog, this post will be displayed, at the very top of the home page. Tomorrow, this post will be displayed, just not at the top of the home page. In a couple weeks, this post will not be displayed on the home page, at all. That is how blogs work. If you want to display anything else, you don't have a blog.

That's the purist position, anyway. A blog is simply a web site with the latest posts displayed on home page (the main page), and hidden older posts (the archives).

---

(Update 2012/06/06): The recent "Search preferences" feature allows us to setup a true static home page, with none of the complications below.

---

The neat thing about this magic trick is that it's not difficult to make it work. I categorise this trick as a snake, after the old taunt from my mother

If it had been a snake, it would have bitten you.

It's so simple, really.

1. Make the blog not display any posts, for home page.
2. Add a text gadget.
3. Tweak the text gadget to only display, when home page URL is displayed.
4. Use the Pages gadget, and index the rest of the blog. Add links using various label searches, pages, and posts, as you like.

Make The Home Page Not Display Any Posts
If you make the main page not display any posts, you get an empty home page. Settings - "Posts and comments" contains the "Show" setting. Set "Show" to "0 posts", and the blog has an empty home page.

Add A Text Gadget
Add an HTML / Text gadget, positioned just above or below the "Blog Posts" gadget. Setup the new gadget just like the blog post, that you would want permanently displayed. If you want to use the post editor to compose the gadget, do that.

Tweak The Template
This is the one part of this project, that requires any technique. Use the Template Editor, and edit the gadget template, for the gadget that you just added, so the gadget only displays when the home page URL is being displayed.

Use The Pages Gadget, To Index The Rest Of The Blog
Once you have a static home page gadget, just add links to the rest of the blog. You can have links in the new gadget - and you can have an index in the blog header, or in the sidebar. Use your imagination here, it's your blog.

That's it. Really.

>> Top

Making Jump Break Work For Blogs With Older Templates

The new Blogger solution for auto summarised posts, also known as "Read More" or "Jump Break", is becoming increasingly popular in Blogger blogs, for several reasons.

• Auto Pagination resulted in display segmentation, caused by the perceived need to publish hundreds of posts on the main page.
• Desire to display a dynamic index of posts as the main page.
• Desire to simply make the main page and / or archive retrieval displays smaller.

The "Jump Break" feature itself is reasonably easy to use, when you are using the New Post Editor, and with blogs that use a template released after Jump Break was released - apparently in September 2009. If your blog was created before then, you may need to add a critical bit of code to the post template.

The simplest way to add the necessary code would be to refresh the post template.

If you have customised your post template, this won't be a good idea. If you want to keep the current post template, and add the critical bit of code, you're going to have to edit the template HTML, and you're going to have to Expand Widget Templates when you edit the HTML.

Instruction from Blogger, in Creating 'After the jump' summaries is pretty simple

After backing up your template, then click the Expand Widget Templates checkbox, and scan your HTML for the following snippet:

<data:post.body/>

Once you've located that code, paste the following snippet directly below it:

<b:if cond='data:post.hasJumpLink'>
<div class='jump-link'>
<a expr:href='data:post.url + "#more"'><data:post.jumpText/></a>
</div>
</b:if >

After you've pasted in the code, click Save and then you're done!

It's possible that such simple instruction may be slightly misleading.

Here's the snippet in question, as seen in the template in my newest test blog, "Chuck's Jump Break Test", with surrounding code to provide a contextual reference.

<div class='post-header'>
<div class='post-header-line-1'/>
</div>

<div class='post-body entry-content'>
<data:post.body/>
<div style='clear: both;'/> <!-- clear for photos floats -->
</div>

<b:if cond='data:post.hasJumpLink'>
<div class='jump-link'>
<a expr:href='data:post.url + "#more"' expr:title='data:post.title'><data:post.jumpText/></a>  
</div>
</b:if>

<div class='post-footer'>
<div class='post-footer-line post-footer-line-1'>
<span class='post-author vcard'>
<b:if cond='data:top.showAuthor'>
<data:top.authorLabel/>
<span class='fn'><data:post.author/></span>
</b:if>
</span>

If you read the above instructions literally, Blogger would have us take an older template

<div class='post-header'>
<div class='post-header-line-1'/>
</div>

<div class='post-body entry-content'>
<data:post.body/>
<div style='clear: both;'/> <!-- clear for photos floats -->
</div>

<div class='post-footer'>
<div class='post-footer-line post-footer-line-1'>
<span class='post-author vcard'>
<b:if cond='data:top.showAuthor'>
<data:top.authorLabel/>
<span class='fn'><data:post.author/></span>
</b:if>
</span>

Add the recommended snippet to produce

<div class='post-header'>
<div class='post-header-line-1'/>
</div>

<div class='post-body entry-content'>
<data:post.body/>
<b:if cond='data:post.hasJumpLink'>
<div class='jump-link'>
<a expr:href='data:post.url + "#more"'><data:post.jumpText/></a>
</div>
</b:if>
<div style='clear: both;'/> <!-- clear for photos floats -->
</div>

<div class='post-footer'>
<div class='post-footer-line post-footer-line-1'>
<span class='post-author vcard'>
<b:if cond='data:top.showAuthor'>
<data:top.authorLabel/>
<span class='fn'><data:post.author/></span>
</b:if>
</span>

I suspect that the update may be much more correctly installed as

<div class='post-header'>
<div class='post-header-line-1'/>
</div>

<div class='post-body entry-content'>
<data:post.body/>
<div style='clear: both;'/> <!-- clear for photos floats -->
</div>

<b:if cond='data:post.hasJumpLink'>
<div class='jump-link'>
<a expr:href='data:post.url + "#more"'><data:post.jumpText/></a>
</div>
</b:if>

<div class='post-footer'>
<div class='post-footer-line post-footer-line-1'>
<span class='post-author vcard'>
<b:if cond='data:top.showAuthor'>
<data:top.authorLabel/>
<span class='fn'><data:post.author/></span>
</b:if>
</span>

Or possibly, you may even want the full, original snippet

<div class='post-header'>
<div class='post-header-line-1'/>
</div>

<div class='post-body entry-content'>
<data:post.body/>
<div style='clear: both;'/> <!-- clear for photos floats -->
</div>

<b:if cond='data:post.hasJumpLink'>
<div class='jump-link'>
<a expr:href='data:post.url + "#more"' expr:title='data:post.title'><data:post.jumpText/></a>
</div>
</b:if>

<div class='post-footer'>
<div class='post-footer-line post-footer-line-1'>
<span class='post-author vcard'>
<b:if cond='data:top.showAuthor'>
<data:top.authorLabel/>
<span class='fn'><data:post.author/></span>
</b:if>
</span>

So, what is "expr:title='data:post.title'"? Look at my demonstration, hover the mouse cursor over "Read more »", and see.

If you just added the Jump Break to your blog after following the instructions from Blogger, and you followed their instructions literally, you may be observing odd details. It's possible that reports of post / sidebar alignment problems, and odd problems with photos and jump break, may be related to this confusion. You may do well to modify their instructions, when you update your template.

>> Top

Classic (HTML) Templates Get A New Lease On Life

As a result from a few (justified) complaints about Auto Pagination and its effects on blogs with classic (HTML) templates, Blogger has released an enhancement which will make classic templates, in general, more usable.

In Creating pagination links on Classic Templates, we see two new options for classic templates.

If you are using Classic Templates and would like to add pagination links to your blog, there are currently two options for setting this up. Both involve adding a snippet of code to your blog's template, which can be done from the Template | Edit HTML tab.

You even have the ability to customise the link caption, with the phrase of your choice, or even a graphic - as you can see on some of my blogs.

• "<$BlogPaginationLinks$>" (for language automatic, "Older / Newer" captioned links).
• "<$NewerPosts$>" / "<$OlderPosts$>" (for manually labeled custom captions).

Anybody with a blog with a classic template will enjoy using these options, and especially those with blogs subject to unwanted display segmentation. You may see my initial test, in my Classic Template Laboratory. Here's my implementation, with copious amount of detail removed.

<!-- Begin #main -->
<div id="main"><div id="main2">

<Blogger>

<BlogDateHeader>
<h2 class="date-header"><$BlogDateHeaderDate$></h2>
</BlogDateHeader>

<!-- Begin .post -->

...

<!-- End .post -->

<!-- Begin #comments -->
<ItemPage>

...

</ItemPage>

<!-- End #comments -->
</Blogger>
</div>
<$BlogPaginationLinks$>
</div>
<!-- End #main -->

You need to insert the extra code at the very end of the "main" section. Note that precise placement, after the right "</div>", is essential.

You'll note that neither "<$BlogPaginationLinks$>" nor "<$NewerPosts$>" / "<$OlderPosts$>" provides the exact functionality of the links that are built in to designer / layout templates. If you want full functionality, you have to upgrade. Fortunately, since FTP Publishing was terminated, there is no real need to remain with classic templates.

>> Top

Static Pages And Comments

After long waiting, Blogger added a static pages option to our blogs. And even as blogger are busy adding static pages to their blogs, they are learning what static pages are - and what they are not. And as we note what static pages are not, we have to note that one feature which they appear to provide - comments - may not work for everybody.

Some bloggers have observed that comments do not work on their static pages. Comments are a complex product, and are sensitive to many settings - both in the blog, and on the client computers.

Right now, we're just starting to look at this deficiency. Help us out here, if you are able.

• First (guess what is first?) what is the URL of the blog with the noted problem?
• Does the blog use Embedded, Popup, or Separate Page comments?
• Is the problem observed on the computer of the blog owner, on the computers of the readers, or all computers?
• If the problem is inconsistently observed on multiple computers, what operating system and browser is in use when the problem is noted? When the problem is not noted?
• Does the blog contain any customisations in the post template?
• Have you tried standard comments diagnostics?

That's where we start. The initial diagnoses start with you, and with what you can tell us.

>> Top

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