Skip to main content

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:include data='post' name='comments'/>
  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


Nance said…
Before I tackle this fix, I notice that threaded comments work perfectly well with my two .blogspot blogs, but do not work with my custom domain blog (purchased through Google).

Jean said…
Before I tackle this, I'd like to know I won't be opening another can of worms!
Faizal Rahman said…
Wondering why you did not use threaded reply?
Chuck Croll said…
Thanks Faizal, you ask a good question.

Many of the people who read this blog, and who benefit from my advice, are using browsers and computers with overly optimistic filtering.

Threaded commenting requires use of the embedded comment form, which is susceptible to cookie filtering problems, caused by layered security settings on peoples computers.

In order to enable more people to comment on this blog, I'm going to avoid use of the embedded comment form.
Seh Wei Jun said…
Finally, a real fix for this one. Thanks a lot buddy <3

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.

Help! I Can't See My Blog!

I just posted to my blog, so I know that it's there. I can tell others are looking at it. But I can't see it.

Well, the good news is you don't have a blog hijack or other calamity. Your blog is not gone.

Apparently, some ISPs are blocking *, or maybe have network configuration or infrastructure problems. You can access or you can access, but you can't access, or

You can't access them directly, that is. If you can access any free, anonymous proxy servers, though, you may be able to access your blog.

Note: You can use PKBlogs with the URL pre packaged. Here is the address of this post (with gratuitous line breaks to prevent the old post sidebar alignment problem):

And an additional URL, to provide to those suffering from this problem, would be the WordPress version of this post: