The Real Blogger Status

We're seeing a problem with Blogger Hosted Comments - and "Bad Request Error 400", following the use of the comment "Preview" feature. When a blog owner or reader composes a long or important comment, use of the Preview feature is normal. Right now, after hitting "Publish", following a successful Preview, one frequently sees the bad news. Bad Request Error 400 There is a workaround for this annoyance - and it's not difficult to use.

One of the most obscure Blogger error messages - next to "Another blog ..." - is the monolithic advice seen on main page display of some blogs. No posts. or maybe There's nothing here! What can you say, to a blog owner who has started a new blog, and spent days publishing blog content - only to view the blog, and see "No posts." - or "There's nothing here!"?

Many blog owners want the legendary wealth, from publishing a Blogger blog, and adding AdSense ads. Not everybody understands the AdSense review process - and the fact that "Congratulations!" is only the beginning .

The Internet is diverse and large - and the Internet directory system, aka the DNS Infrastructure, supports the diversity and size. When we setup a new domain, the registrar frequently advises us to wait patiently, before continuing. Congrats on your new domain! Now, we suggest that you wait 24 - 48 hours for the new domain to propagate, before trying to publish to the domain. When we update a domain - and add or delete a single DNS address - we won't always get advice about waiting, from the registrar.

As most of us know, Blogger HTTPS support does not include custom domain publishing . The advantages offered by HTTPS access are widely advertised - and have led to envy between blog owners who publish to custom domains, and native BlogSpot blog owners proudly advertising their new HTTPS connectivity. Long ago, we saw possibly malicious code which helps our readers avoid using country code aliases , to read our blogs from an aliased country. Recently, there was dodgy code which blocked HTTPS mode , to read a customised blog. Now, we have custom code to force HTTPS access, for BlogSpot published blogs.

Sometimes, we need to remove a page or post from a blog - but prefer to not delete it. There are various reasons for not wanting to delete a page / post immediately or permanently - maybe when removing a post for problem diagnosis , or to change the URL to match the publish date . Reverting to draft status is easily reversed, and has no permanent side effects. When you want to quickly - but not permanently - remove a page or post, you can revert to draft status.

Some blog owners, who publish multiple blogs with different subjects, may decide that some subjects would be better discussed in a different blog. With various posts published in one blog, the owner may decide that those posts should be published in a different blog, to continue discussion. The question now is how to move posts, from one blog to another? The dashboard "Export / Import" feature, which is now labeled "Import & back up" , lets us copy pages and posts from one blog to another. Just copying all pages and posts, though, will create problems with duplicated content.