Chrome Browser, And Elegant Disappearing Scroll Tabs

The disappearing scroll tab, in the latest Chrome browser version, is tres elegante - for some blog owners.

Personally, I'm not convinced.

Hover the cursor in the scroll tab area, to get the tab to pop out.

If you use the Chrome browser, and the display content is longer (or wider) than one physical screen, you may not realise that.

Some people may think that part of their blog - their post - or their template - has been lost.

But, look again.

Now, you see it.

Now, you don't.



If you use a "mouse" with a scroll wheel, this is not a problem. Start scrolling with the wheel, and the tab pops out.

For folks who are accustomed to "grabbing" the tab, and dragging it downwards (sideways) to scroll, this is not a step forwards. If you want to read text, that's above the bottom of the blog, how do you scroll left to right, while reading a long line of text?

Look at what our readers see.

Now, you see it.

Now, you don't.



Where did the rest of my main page go??

What our readers think, when using Chrome, is another question.

I think that the scroll tab is another "well enough".

Now, you see it.

Now, you don't.



Where is the rest of my post code? What the #@!!?

At any rate, if you - or your readers - think that blog, post, or template content has mysteriously vanished, try using the scroll tab (if you can find the tab). You may find the "missing" content, right in front of you.

---

The Chrome Engineers recently added an elegant enhancement to their browser. If you're not scrolling up and down (or right to left), you don't have to look at that nasty old scroll tab - even when using the #Blogger post editor.

I'm not convinced that this is a step forward.

Post Editor Displays A Bogus Error When Updating Posts

Some blog owners report a problem with editing posts, in post editor.

With any changes made to a published post, an attempt to update shows another monolithic error.

An error occurred while trying to save or publish your post. Please try again.

But the mystery does not end there. Even seeing the error, a curious blog owner, refreshing the post as displayed, may find a surprise.

Even with the mysterious error displayed, repeatedly, the changes just made may be visible in the post.

In some cases, a new post editor session - or the post display refreshed - will even show the changes made.

Even with the post editor showing

An error occurred while trying to save or publish your post. Please try again.

you may see your changes displayed, when you refresh the displayed post.

I just updated my earlier post, Country Code Aliasing Is A Solution - Not A Problem.

My personal and recent experience.

The post, before being updated.



I added the observation to the post

Blogger has described the problem, as a solution to free expression and controversial content.

to the post.

I just updated my post.

Post Editor, showing the added observation.



Then, I clicked "Update" - and waited for an eternity. No matter how many times I hit "Update", I see the same error.

It's enough to make one pull hair, in anguish (as if, Chuck!).

Post Editor, showing the added observation, after clicking "Update".



But, the story does not end here.

The post, after being updated - even with the bogus error message displayed.
Surprise! See the added observation?



Don't believe me? Examine my post, Country Code Aliasing Is A Solution - Not A Problem.

If you see the error, don't give up!

So, if you edit your post, and having made the necessary changes, you see the bad news

An error occurred while trying to save or publish your post. Please try again.

don't pull your hair in anguish, immediately.

Refresh the post - then examine the updated display, and the change just made (in a separate tab / window). You may find your changes saved, as if nothing is wrong.

And, it's the EverReady Bunny problem of the week.

I was once again, updating my previous post, and idly wondering if this problem had been fixed - and hello!

Post Editor, showing this error, after clicking "Update" - just as I updated my previous post.

My previous post - updated, even with Post Editor displaying the error!



This, too, may involve the Blogger / Google CDN - and delay in updating the Blogger database, between the nodes in the CDN.

Just be careful when closing the post editor tab or window, with the warning about unsaved changes displayed.

So, what to do, now? I couldn't even leave that window, to update this post - I had to Stay!


And having updated this post, in this window, I have to close that window, with the changes maybe unsaved. But I'll re read the post as displayed, first.

---

If you see a mysterious #Blogger Post Editor error "An error occurred while trying to save or publish your post. Please try again.", when trying to update a previously published post, repeatedly, take a moment and verify that the changes being made were NOT saved. You may be surprised!

This, too, may involve the Blogger / Google CDN - and delay in updating the #Blogger database, between the nodes in the CDN.

Revert A Page / Post To Draft Status

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.

Reverting to draft status is convenient, safe, and simple.

You can revert a page or post using Page / Post Editor, or the Pages / Posts dashboard page.

• Revert, using the Pages / Posts dashboard pages.
• Revert, using the Page Editor / Post Editor.

Revert, using the Pages / Posts dashboard pages.

The Pages / Posts dashboard page is a menu. Simply select one or more pages or posts, then click "Revert to draft". Click on "Yes" to verify. and you're done.

Hit "Revert to draft", after selecting a page or post.



Revert, using the Page Editor / Post Editor.

Any time that you are editing a previously published page or post, click "Revert to draft". And you're done.

Hit "Revert to draft", when in page / post editor.



And when you're done, you're done.

Once a post is newly draft, it's offline. Page / post content in cache on your readers's computers will be readable until it expires. New readers, on the other hand, will see a "404" immediately.

You can recover the post with the URL - or rename to a new URL.

If you revert to draft - then later, re publish without changing the title, you will get the same post, with the same URL, back. If you change the title with the post in draft status, you get the same post content, under a new URL, when you re publish.

If you do the latter by mistake - then discover the mistake later, you can recover the mistake by merging the new and previous URLs. Just add a custom redirect from the new to old URL (or vice versa).

Review / Recover The Draft Inventory, With One Mouse Click

Any time that you need, review the inventory of Draft posts. Just click on "Draft" under "Posts". You can Edit then Publish - or just Publish, immediately.

Check out the current Draft posts complement, from Pages or Posts - Draft. Then recover one or more.

Just select one or more posts, then "Publish".

Or edit a page or post, then Publish.



Either way, you can recover any pages or posts, reverted, easily enough - as long as you revert them, instead of deleting them.

Just understand the possibilities.

---

Reverting a #Blogger blog post to draft status is a quick, yet reversible, way to take a post offline. The URL will be recovered, automatically - as long as you do not change the title.

Post Editor Generates An Extra Post?

Recently, we have some blog owners observing that use of Post Editor leads to generation of an extra draft post.

If I edit this post, then save my changes, I may see an empty post when I hit "Close".

So, we will see. I will next Save this post, as is.

Here's this post, initially created.

And this post, being Edited.



Having added the above screen prints, I'll Save again.

And if I Save, then Close, I see an empty post.



The "empty" post, shown above, is normal for this blog - which uses dashboard "post template" content in new posts.

If I were to Save this new post, I would end up with an extra draft post. Since I don't care to Save, I will simply hit Close.

And when I Edit, then Save, there's the bogey, again.

This time, I Save - or wait until AutoSave kicks in.

And look at my Posts display.



And hitting Publish, I get another.

Here we see possibility for real confusion.



Be careful, and think - if this happens to you!

If you Save instinctively - or if you hesitate, and AutoSave activates, you end up with an extra draft post.

Be really careful, now!

The bogey is an "empty" post (with "post template" content).

Even with the bogey being "empty", look at the Posts list! If you Edit your post later, always make sure that you Edit the right post - with your updated content!!



If you end up with an extra draft post, be very careful to Delete or Edit the right post. Think carefully, before you continue!

Anyway, this problem is in the hands of Blogger Engineering.

Just don't Save - hit Close, immediately - and you'll see no long term weirdness. Until you Edit, again, of course.

---

This weekend, we see #Blogger Post Editor adding an extra post, when we Edit then Save a draft post. If you Close the unwanted post immediately, you'll see no lasting effects, however.

Blogger Magic - Updating Labels

Not all blog owners know the best ways to update labels, with the posts in their blog.

We see occasional signs of confusion, in Blogger Help Forum: Learn More About Blogger.

How do I add a label, to many posts at once?

and

How do I correct the spelling of my label, already added?

and

How do I remove all of the labels, from one of my posts?

These owners are not aware how to use the dashboard Posts page - and Post Editor - to add, delete, and edit labels.

Blogger gives us labels (aka "categories") - and two ways to manage labels.

You choose the appropriate procedure, based on what changes are needed. The difference is whether you have one label, that needs to be applied to many posts - or one post, that needs multiple labels applied.

1. Using the dashboard Posts page - one label, many posts.
2. Using Post Editor - many labels, one post.

Using the dashboard Posts page - one label, many posts.

The Posts page, and the Posts menu, is used to add, delete, and edit one label, for many posts - one label, at a time.

1. Use the Label Selection list, to select the posts to display.
2. Use the Posts Selector column, to select any or all posts displayed, for action.
3. Use the Label Action list to add, delete, or edit a given label, for the selected posts.
• To add a label, click on "New label...", type the new label, enter the new label, and click "OK".
• To delete a label, click on any label that has previously been applied to all posts selected. With any one post selected that does not have the label clicked, that label will be added as necessary.
• To edit a label, you have a slightly more complicated procedure.
4. Repeat as necessary, for another label.

The Posts page.

Open the Label Selection list, by clicking on the pulldown arrow.

Select the posts for the label needed.

Use the Posts Selector column, to select any individual posts, or all posts, for action.

Open the Label Action list, by clicking on the pulldown arrow.

Add a label, using "New label" - or delete or edit a label, by selecting one of the listed labels.



Editing the name of one label, for many posts, requires adding a new label - then removing the old label. This is a slightly more complicated procedure - and is subject to label related limits. "Editing" a label, using the Posts page, will require planning, in some cases.

Using Post Editor - many labels, one post.

Post Editor is used to add, delete, and edit many labels, for one post - one post at a time.

1. Find and select the "Labels" caption, in the "Post settings" sidebar.
2. In the window that opens, add, delete, and edit as necessary.
3. Click "Done".
4. Click"Update".

Select "Labels", in the sidebar.

Add, delete, and / or edit the label cloud.



If you have multiple labels, in multiple posts, that need changing, you can use a combination of the above techniques.

Beware the label limits.

When updating labels, you need to avoid exceeding the limits.

• Per blog label count.
• Per post label count.
• Per post label character count.

If you exceed a limit, you may have less choices than you would want. If your changes are extensive, you may do well to script the task, before starting.

---

Making label changes, to multiple labels and / or posts, in a #Blogger blog, can be done using either the dashboard Posts page or Post Editor. There are reasons for choosing either alternative.

HTTPS Redirect And Post Editor HTTPS Warnings

Last month, as part of the SSL rollout, Blogger added a page / post / template editor feature - that not everybody understands.

A blog with "HTTPS Redirect" enabled will provide SSL access, for every reader - both those who intentionally use HTTPS, and those who normally use classic "HTTP". Those who normally use "HTTP" will find themselves redirected to "HTTPS" - no choice.

When you use page editor, post editor, or template editor, on a blog which offers "HTTPS" to everybody, you may see an alarming alert.

If you decide to enable "HTTPS Redirect" on your blog, page editor, post editor, and template editor will let you know when you are editing mixed content.

This page contains HTTP resources which may cause mixed content affecting security and user experience if blog is viewed over HTTPS.

When editing pages and posts, on a blog with "HTTPS Redirect" enabled.

Editing your template so it mixes HTTP and HTTPS may affect the security and user experience of your blog when it is viewed over HTTPS. Learn more. Hide warning

And when editing the template, on a blog with "HTTPS Redirect" enabled.



You will have several choices, when encountering the "This page contains HTTP resources ..." / "Editing your template so it mixes HTTP and HTTPS" alert.

• Change all links to "HTTPS:", using "Fix".
• Fix each link selectively, and select "Dismiss".
• Don't change anything, and select "Dismiss".
• Don't enable "HTTPS Redirect".

Change all links to "HTTPS:", using "Fix".

Select "Fix" - and page / post / template editor will automatically change every "http:" reference to "https:".

You will have broken links, which reference services and websites that do not yet support SSL. You will eventually need to find out what services and websites you link and use, that don't provide SSL - and drop them, or encourage them to upgrade.

Fix each link selectively, and select "Dismiss".

You will have broken links, which reference services and websites that do not yet support SSL. The links that you leave as "HTTP:" will still throw "Mixed Content" warnings.

Don't change anything, and select "Dismiss".

Your blog will throw "Mixed Content" warnings.

Don't enable "HTTPS Redirect".

Let your readers decide how to access the blog. The readers who use HTTPS will see "Mixed Content" warnings.

"Mixed Content" warnings will be around, for a while.

Until all blogs, services, and websites provide SSL, every blog and website that links to or uses those blogs, services, and websites is going to throw "Mixed Content" warnings.

The purpose of the warnings is to let the readers of our blogs know of possible risk.

Hey! This blog has content that may not fully support your need for security!!

That's what the warnings are designed to do. Keep our readers informed, so they can protect themselves.

---

Not every blog owner knows what to do, when using #Blogger page, post, or template editor, and encountering the Blogger equivalent of a "Mixed Content" alert. Blogs that have the recently added "HTTP Redirect" option enabled will be susceptible to this alert.

https://productforums.google.com/forum/#!category-topic/blogger/SHhkzy1uh8g

Blogger Provides A Mixed Content Detection Tool

In the process of publishing my earlier post "Blogger Magic - Add An HTML Gadget", I discovered the latest feature in the Blogger SSL upgrade.

Page / Post Editor now scans page / post content, and warns us when there are links still using "http" protocol. This will help us avoid publishing pages and posts which will generate "Mixed Content" warnings, when pages and posts are displayed using SSL.

The new post editor tool will help us avoid subjecting our readers to unexpected "Mixed Content" warnings.

We will be responsible for finding out what specific content can be accessed, using SSL. If we believe that a significant proportion of the identified page / post content can be accessed using SSL, we can have all content automatically changed from "http" to "https" - then deal with individual access problems.

The "Fix" link will change all "http:" links to "https:".



If you believe that all links, currently accessed using "http", can be accessed using "https", you can use the "Fix" link. Otherwise, use "Dismiss", then manually change individual links.

Alternately, use a browser based "string find" tool, as available, and identify each instance of "http:".

If you change an individual link, or use the "Fix" option - and you change to "HTTPS" for a blog, service, or website that does not support SSL - that blog, service, or website reference will break. So edit carefully! Only you can decide if broken gadgets / links are better than "Mixed Content" alerts.

The "Dismiss" link lets you evaluate each "http:" link, using the browser "find" wizard.

Then, make your own decision.

Using either "Dismiss" or "Fix", you are responsible for each link - if you want your readers to get results from each link that you provide.



Click on "Learn more", for more information, in Blogger Help: Fix mixed content on your blog.

Which ever you choose, your readers benefit should be your guiding force.

---

As part of providing SSL connectivity for our blogs, #Blogger now provides an "http:" detector, in post editor. The blog owner has the choice to change each "http:" link in the post automatically - or to manually evaluate change each link, and change when appropriate.

Editing An Old Post? Beware Missing "</li>" Tags!

I recently updated an old post, to add a link to a newly published post - and experienced panic.

Adding a link to an old post, Deleted / Locked Blogs Have Several Causes, I discovered an oddity which caused extreme heartburn for several hours. Maybe you have experienced this, also.

Editing my post, and adding a simple single sentence, with embedded link, at the end of the post, I refreshed the display (always test your changes - no matter how minor!), and watched as the paragraphing scrambled itself.

I added a single sentence to the end of an old post - and watched as paragraphs in the post became hopelessly scrambled.

See the missing "</li>" at the end of the first list element?

Look at how the list line spacing is screwy now.

<li><a href="#DMCA">DMCA Violation</a> looks for copyright and similar violations.

Just one missing tag. Long ago, I learned to always close every list element properly.

<li><a href="#DMCA">DMCA Violation</a> looks for copyright and similar violations.</li>

But my proper list syntax policy had apparently started after the post, in question, was published.

I spent the next 1/2 hour re paragraphing the post content, following the broken list - and re spacing the list itself.

And having saved my work, the list - and the paragraphs following the list - remained scrambled.

This is no good!

How can I hope to help people, using this post?



Observing that paragraphing above the broken list was fine, I looked at the list code, line by line.

Paragraphing above the list is OK!



Much to my relief, I found a missing "</li>" tag. Adding the missing tag, I re paragraphed the post content - and this time, my changes remained.

This is what I would want to see.

Even the list remains properly spaced, in post editor.



Be very careful, when editing lists, in post editor "HTML" mode. Lack of care can lead to unpleasant consequence.

---

When editing a #Blogger blog post, in HTML mode, be very careful to avoid dropping closing list element tags. One dropped tag affects formatting of list content after the missing tag - and paragraphing following the broken list, even with the list properly closed.

target="_blank"

Base64 Photo Hosting, And Open Graph Code

Some blog owners make photos an important part of blog content.

When sharing a post to FaceBook, problems are seen with photo content. In some cases, this is because of how the photos were added into the post, when using Post Editor.

We've known about problems with photos installed using drag and drop, and post editor, for a few years. Drag and Drop photos, in some cases, are stored as "Base64" content - with the photo content hosted in the post, instead of Google Photos (or Picasa).

Photos added to posts in post editor, using "drag and drop", have been a problem for many years.

Base64 hosted photos make posts abnormally large.

Posts containing "Base64" encoded photos are abnormally large - and will cause problems with the index pages, and auto pagination. That is a nuisance - but just that.

With posts shared to social media, such as FaceBook and Twitter, photos hosted using Base64 become more than a nuisance. When normal posts are shared to FaceBook, OpenGraph code is used to identify key post content - such as a photo to accompany the shared post.

Open Graph code uses URLs to reference photos.

OG code uses HTML / XML tags, in template code - with a URL identifying a shared photo. A post that contains Base64 hosted photos won't have URLs identifying the photos - it will have the actual photo content.

This photo was installed, using drag and drop. Interestingly enough, it is not Base64. It is possible that Blogger no longer uses Base64 encoding - which would explain why the problem with OG code is rather irregular.

When shared to FaceBook, the photo must be converted to normal Google Photo hosted content, so it can be shared using a URL - as normal photos are shared, using OG code. If shared using Base64 content (if OG were to support Base64), the post, again, becomes abnormally large.

Base64 hosted photos simply present one more complication, when sharing posts to FaceBook, Twitter, and other social services.

---

Some blog owners publish posts that contain photos added using drag and drop. Some drag and drop installs result in Base64 hosted photos - which must be converted to Google Photos hosted content, when shared to FaceBook or Twitter.

Correct Your Post, After Using MS Word

Sometimes, advice provided in Blogger Help Forum: Get Help with an Issue, comes too late.

Telling people to avoid use of MS Word, for composing posts, is one example of "too late". But maybe this delinquency can be repaired.

Blogger provides the the page / post editor "Remove formatting" tool ("Tx"), for removing unwanted formatting.

When you've just published your post - and can't figure out why the formatting is all whacky - or maybe you can't get the post successfully passed through a FeedBurner feed - the most obvious way to correct the post is to use Notepad, or a similar text editor.

But that's a pain, and it's rather complicated. Maybe there's an easier solution.

Like an over edited post - or a victim of too much switching between Compose and HTML modes - the "Remove formatting" tool ("Tx") might save you, here.

Select everything in the page / post.

And use the editor "Remove formatting" tool ("Tx").


As in the previous example, you may have to spend a few hours adding essential formatting back. But with MS Word meta formatting, aren't you better off getting rid of all of that, at once?

---

Some #Blogger blog owners publish posts full of junk meta formatting, courtesy of MS Word - then look for a quick solution. Copying out then back, using Notepad / WordPad, or a similar text editor is the most obvious solution - but it's a painfully complicated one.

Maybe this is another case when the page / post editor "Remove formatting" tool can save the day.