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

Read More

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.

Read More

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

Read More

Third Party Templates - Not Always Free

Some third party templates come with extra features - that not everybody appreciates.

How do I get rid of the "lorem ipsum" nonsense, that's part of my signature?

This blog owner just got a shiny "free" third party template, for her blog.

Some custom template providers publish free templates that contain odd, irrelevant details.

When I click on the "Read more" link on my blog, it opens up the post - but has added in a odd kind of signature. It displays my name but is using an image that isn't me, and the "lorem ipsum" text. I have no idea where to edit this?

The typical response, by experienced forum helpers, will be a simple suggestion.

Hopefully, the template publisher can sort the problem. If not, a standard Blogger template, or a different third-party template, may be your best solution.

That's a reply, based on experience.

This particular template oddity has been mentioned, in Blogger Help Forum: Get Help with an Issue, a few times - each time with mention of the "lorem ipsum" babble, in the signature.

In one case, the blog owner did contact the template developer - and was kind enough to follow up in her forum thread.

She told me that she would be glad to provide a clean template - for a fee.

It's likely that the "bogus photo" / "lorem ipsum" bit is there, to motivate the blog owner into paying for the template.

In a way, this sort of "fee based" customisation makes sense. The blog owner has 3 choices.

1. Pay extra for the template cleanup.
2. Get a different third party template, from a different provider.
3. Learn to live with the irrelevant babble.

Neither the bogus photo, or the babble, damage the blog. The content is there, as desired - and pleasantly displayed. Not too many blog readers will know that the photo is bogus, or care so much about "lorem ipsum", either.

In a way, it's similar to the legendary photos of imaginary family, that one gets when buying a fancy picture frame, or a new wallet. Some (single, and very lonely) people like the photos - and supposedly, keep them when using the wallets.

Maybe new blog owners won't care, either. They are, after all, rather attractive templates - and popular with women, anyway.

The apocryphal signature section.

The source code for the signature section.



Enjoy the new templates. Pay, when the need arises. Or, refresh the post template (possibly, lose a lot of custom formatting, if you do) - but this should get rid of the "lorem ipsum" nonsense.

---

Some non #Blogger supplied templates are provided for a price - and payment is optional, though cleverly motivated. Minor irrelevant content is included, which is most noticeable to blog owners who are publishing blogs with a large and observant reader population.

Conversely, the unwanted content is not important to new blog owners who would appreciate the free templates, which are not noticeably damaged by the irrelevant content.

Read More

bX Codes, Diagnosing "Error 500", Being Reported

We're seeing a few reports from blog owners, in Blogger Help Forum: Get Help with an Issue, with blogs being inaccessible.

My blog can't be seen at all, it just says error when I'm trying to open my blog. I also can't edit anything, like HTML or Template.

When the blog is viewed, it will issue one of several bX codes. So far, I've identified bX-3o92c2, bX-ppgc07, bX-tqn3zr, bX-v2vqfh, bX-vg1g6a. When the blog is viewed, using an HTTP trace, the trace will terminate, showing an old friend.

Error 500 Internal Server Error

What we appear to be seeing is multiple bX codes, being used to diagnose the various causes of the "Error 500", which has long plagued Blogger blog owners.

The "bX-v2vqfh" and other errors appear to be "500 Internal Server Error".

Here, we see a "bX-vg1g6a".

And an HTTP trace, for the same blog, shows the ubiquitous "Error 500 Internal Server Error".



So, the blog owner should get a new template - or restore from backup.

The simplest solution, to the "Error 500" has been to restore the template, from a recent backup - hoping that you have a usable backup. If a backup is not available - or if the blog, with the backup applied, also returns a bX code - you must get a new template.

The fortunate blog owner, able to login to Blogger with the right account, will have a relatively simple task.

1. Click on the "Design" link in the navbar.
2. Choose a new template - or restore from a previous backup.
3. Use "Edit HTML", and reset the post template.

If the blog has a custom template, that cannot (should not) be trashed, and the Template page can be accessed, a backup before getting a new Blogger template - and a restore after - may provide relief.

In either case, you will need to use the dashboard Template page - then reset the post template, using Template "Edit HTML".

In some cases, the dashboard can't be accessed. In this case, we must (with some effort) access the Template page, directly.

Possibly a little effort may be required.

1. Extract the BlogID, from the navbar "Design" or "New Post" link.
2. Build a Template page access URL.
3. Access the Template page, using the direct URL.
4. Choose a new template - or restore from a previous backup.
5. Use "Edit HTML", and reset the post template.

If the navbar link can't be used, a little more work is involved.

1. Find a cached copy of the blog, before the template broke.
2. Extract the BlogID, from the cache source code.
3. Build a Template page access URL.
4. Access the Template page, using the direct URL.
5. Choose a new template - or restore from a previous backup.
6. Use "Edit HTML", and reset the post template.

Finally, if possible, recall what changes you made, immediately before the problem was observed - and avoid repeating those changes.

Note that some blogs absolutely won't provide access to the Template page - but they may, to the Template Editor aka "Edit HTML".

---

It appears that #Blogger Engineering, in an effort to diagnose the annoying "Error 500 Internal Server Error", has recently activated or added a series of bX codes - which are being reported by various blog owners.

We were some time ago advised to have the owner get a new template, when encountering the "Error 500".

Read More

Unfold Widgets Selectively, Instead Of All At Once

The new Template HTML Editor has been with us for just under 2 weeks.

Not every blog owner sees the new editor as an improvement. Some folks don't understand how to find the code sections, where they need to apply changes - and would probably be happier if "Expand All Widgets" were an option.

Like the old saying goes, you just cannot please everybody.

Fortunately, with this change, it's not difficult to find the code sections that need changing - you just do a little bit of research, before using "Edit HTML".

With the old editor, finding a section that needed changing could be a bit frustrating - though simple, given enough time.

1. Hit "Expand Widget Templates".
2. Search for a recognisable section of code.
3. Try very carefully, to find the right section of code.
4. Be careful, and don't select the wrong section of code.

With the new editor, you have a bit more work to do - and what you have to do appears to be simply repetitive.

1. Find a folded code section.
2. Unfold the section that's folded.
3. Repeat, until everything is visible.
4. Search for a recognisable section of code.
5. Try very carefully, to find the right section of code.
6. Be careful, and don't select the wrong section of code.

Instead of spending so much time unfolding, searching, and rechecking everything, why not do some research? Figure out what needs changing. Look at the display on the dashboard Layout wizard (previously called "Page Elements"). Identify the widget to be changed, using both the relative position on the page, and the title.

Find the widget id, by looking at the widget to be changed, then at the URL behind the "Edit" link. If you're editing the post template, you'll be looking at "Blog Posts", which has the widgetID of "Blog1". Click here, for instructions on determining the widget id.

Once you have the widgetID, for the specific widget that you need to modify, go to the Template "Edit HTML" wizard, use the "Jump to widget" pull down list, select the widget by widgetID, and there it is. Now, unfold that widget, and do what you have to do.

Isn't that simpler, when you think about it?

>> Top

Read More

Consider, Carefully, The Decision To Use A Third Party Commenting System In Your Blog

Not all Blogger blog owners appreciate the features provided, in Blogger native commenting.

Some suggest that third party commenting systems, such as Disqus, provide a superior service. It's possible that, to some, third party commenting systems are more feature rich - but only Blogger native commenting provides one essential feature, in comment moderation.

Blogger commenting is one component, in the global Blogger / Google spam classification and mitigation strategy.

Blogger blog classification, Blogger commenting moderation, and various Google services, all contribute globally to spam detection, and to spam removal, in Google Internet space. Each service both provides input into - and accepts input from - other services.

Third party commenting products, while they may have some interesting design features that Blogger won't include, won't necessarily contribute to the Blogger blog spam classification effort, or to the community commenting moderation process. Nor will they accept input from Blogger blog spam classification, or from the community comment moderation process.

If you, as a blog owner, believe that Disqus - or other non Blogger commenting products - provides more useful service to your blog, you're entitled to use any service, that you can make work, in your blog. It is, after all, your blog - and this is one feature in our blogs which Blogger / Google leave to our discretion.

As with all third party accessories and services, however, you will get limited support, for any problems. If you break your blog, you'll have only yourself (or the provider of the third party service) to support your problems. You may even see the blog deleted or locked, because of suspected malware.

When you use a third party commenting system, there are two details to consider.

1. Integration of existing comments.
2. Post template modification.

When you install a third party commenting service, you'll have the service import existing comments into their database. And, you will have to install the necessary code into the post template - and deal with ongoing changes to the post template, in the future.

If, in the future, you want to return to use of Blogger commenting, you'll have both of the above details to consider, in reverse. Third party services, while they may provide importation of Blogger comments into their database, may not provide a reverse service. Nor are they likely to provide easy reversal of post template changes - particularly as the Blogger post template may have been changed after installation of the third party service.

If your blog uses an alternate product like Disqus, right now, you'll probably find it easiest to refresh the post template, to return to Blogger comments. If you have various custom tweaks in the post layout, you may not find this to be a pleasant solution.

If you are contemplating changing your blog, to use Disqus - or another alternate commenting system - you may do well to consider all of these issues, before changing.

>> Top

Read More

Template Designer Upgrades Require Supporting Updates To The Individual Blog Templates

This week, we're seeing a small flood of problem reports in Blogger Help Forum: Something Is Broken about problems with the Template Designer.

Every time I change something, I have to refresh the page in order for it to show up. It won't "Save" when I try to save the layout changes. It just says "Saving..." at the top of the page and fades away, but doesn't actually save any changes.

Many problems involve changes made to the template, using the Designer, which aren't being saved - or are broken when saved. Most of the people reporting these problems have made changes to the template, previously - some are so experienced at making changes, they can't believe that their latest changes could ever have problems.

Interestingly, this history of changes is not a coincidence - and it's likely that some of the changes helps to cause these problems.

Take a look at the template code in your blog, some time. You'll notice a lot of code which doesn't look like CSS, HTML, or XML. Some of it is code which supports the various blog features that are adjusted or configured using the Template Designer.

Many template features involve two sets of code.

1. The Template Designer wizard, part of the Blogger dashboard, is common code used by all blog owners.
2. The blog template, post template, and / or widget template, is part of the individual blogs. Some template code does nothing but support the Template Designer - and let you configure your blog layout,

Every time Blogger Engineering adds or updates template features, they have to make changes to both sets of code.

Blogger Engineering does not edit each individual blog, after they upgrade the Template Designer. They make changes to the master template code - and their changes replicate into the individual blog templates. These changes replicate much more consistently, when the individual templates have not been changed.

The more custom a template is, with changes applied by the blog owner, or possibly in a third party template, the less likely it is to properly update, to support each succeeding Template Designer update.

Any time Blogger Engineering updates the Template Designer, to add a new feature, or maybe to support a new browser version, their updates may require changes which are not properly applied to all blogs - and the Template Designer stops working, in some blogs.

When the Template Designer stops working, the usual recommendation is to refresh the post or widget template - or maybe to upgrade the blog template - and things start rolling again. And the blog owner goes back to tweaking the template, until something breaks again.

>> Top

Read More