Skip to main content

Check Your Post Editor "Sticky" Options Settings

People ask, in Blogger Help Forum: Get Help with an Issue, about problems with post formatting.
Why don't all of my posts allow comments?
Why are my posts a mess of code, in one huge paragraph?
Both of these problems can involve post editor Options settings - and in many cases, Options settings from a previous post.

We say that the post editor options are "sticky", because they are retained, from post to post. If you edited the last post, and Published it with "Line breaks" selected as "Use <br> tag", the next post, by default, will have "Line breaks" selected as "Use <br> tag".

Comment settings are both per blog, and per post.

Comments have a per blog setting.

"Hide" prevents all comments - and the comment form - from being shown, in the blog. Anything else - "Embedded", "Full page", or "Popup window" - is subject to the per post setting.

Including comments, there are 4 per post option settings that should concern you.

The other selections under "Post settings" - "Options" are set in post editor, only.

Here are the settings, when this post was Published. These will probably be the same, for the next post.

If you have a problem with one post - and you find the problem includes other posts - you may have to edit each already published post, one by one, and check the settings for each post. Change settings, as necessary.

The Options settings are all sticky, from post to post - with new posts.

All 4 Options are sticky, from post to post.

Note that the stickiness applies to publishing a new post. The setting may or may not be retained, when editing posts - and it won't affect previously published posts.

If you're in the habit of publishing posts, back dated, you'll end up with posts created out of sequence with their display dates. If you change post editor options, from time to time, you'll want to check them, each time you publish a new post.

Keep an eye on the settings, from post to post, for stress reduction.

If you don't check the settings - and if you have some posts with different settings - you will wind up with multiple different per post settings. The havoc created, from unpredictably different settings, will make maintaining your blog a real challenge.

With differing "Reader comments" and "Backlinks", your readers will be periodically noting the inconsistencies. And with "Compose mode" and "Line breaks" changing, from post to post, you'll be busy fixing problems.

If you don't want your posts (some of your posts) irregularly formatted or missing features, make all selections in Post settings - Options consistent.


M. J. Joachim said…
This helps a lot. Thanks!

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: