Skip to main content

Not All Plugins And Third Party Code Support SSL

With Blogger now providing (optional) HTTPS, on all blogs, we're seeing a few anxious reports in Blogger Help Forum: Get Help with an Issue.
I'm getting an error, on one of my plugins.
This content is not yet available over encrypted connections.
What can I do?
The answer won't be encouraging.
Don't enable "HTTPS Redirect", on your blog.
This won't mean that the plugin will work, if your readers choose to use SSL, to access your blog, unfortunately.

One of the reasons why it is taking Blogger so long to get SSL working, is that they have to allow for our blogs, using non Blogger code.

Too many Blogger blogs use non Blogger code that does not support SSL.

One of the reasons, why all websites don't have HTTPS yet, is they have to wait for other websites to provide it.

It's similar to the game of Pickup Sticks. You can't (shouldn't) upgrade your blog, until your accessories and plugins support SSL.

Somebody else may depend upon content from your blog - and his website can't be upgraded, because his website throws a Mixed Content alert, because of his link to your blog. And a third website must wait, for him to upgrade his website.

Your blog may use a plugin that does not provide SSL access.

For plugins that don't support SSL, you may have to choose between having a broken plugin - or dropping use of those services, until they, too, can upgrade. Or don't force HTTPS.


Don't enable the "HTTPS Redirect" option, if you use plugins in your blog, that don't support SSL.



Be patient - and work on blog content.


Be patient. Encourage the websites, that you depend upon, to enable SSL on their service - then you can do the same, with your blog. And keep publishing your blog.

Encourage Blogger to restore the "HTTPS Availability" option. Make SSL access optional, for each blog - not forced SSL optional.



With #Blogger having enabled HTTPS on all BlogSpot published blogs, blog owners are seeing problems caused by non Google websites that don't offer SSL yet. The "HTTPS Redirect" option really should be "HTTPS Availability", again.

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

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

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

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

Comments

Popular posts from this blog

Custom Domain Migration - Managing The Traffic

Your blog depends upon traffic for its success.

Anything that affects the traffic to your blog, such as any change in the URL, affects the success of your blog. Publishing the blog to a custom domain, like renaming the blog, will affect traffic to your blog. The effects of the change will vary from blog to blog, because of the different traffic to every different blog.Followers. People who find your blog because of recommendations by other people.Search engines. Robotic processes which methodically surf your blog, and provide dynamic indexing to people who search for information.Subscribers. People who read your content from their newsfeed reader, such as the dashboard Reading List.Viewers. People who read your content from their browser.No two blogs are the same - and no two blogs will have the same combinations of traffic sources.

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.