}

Saturday, November 18, 2017

Finding and fixing a Disqus problem

This blog uses Disqus commenting system, a free service that replaces the built-in commenting system for Google’s Blogspot/Blogger blogs. For the most part it’s worked well, though there have been sometimes been glitches that needed to be fixed. Today I discovered a new one I had to fix.

My installed Firefox recently automatically upgraded to the latest version, 57, which they’ve named Firefox Quantum, reputedly now the fastest browser available. When I accessed my blog, commenting wasn’t available, not even on posts that I knew had comments. I tried accessing a post with comments by itself, which always used to make comments appear, but that didn’t work. However, the comments were there on Chrome, so I knew the problem was with Firefox.

Without getting overly detailed (I’m happy to provide more details in the comments—just ask), I restarted Firefox in “Safe Mode”, which strips it back to basics and disables all add-ons (aka extensions). Comments reappeared. So, I then restarted Firefox normally, disabled all add-ons, restarted, and then re-enabled add-ons one at a time at repeated until I found the culprit.

It turned out it was “HTTPS Everywhere”, an add-on from EFF (the Electronic Frontier Foundation) that “encrypts your communications with many major websites, making your browsing more secure.” That add-on apparently blocks Disqus. Of course, this isn’t the first time this has caused me problems: In 2013 it was much worse.

With “HTTPS Everywhere” disabled, comments loaded normally. So next I went to Chrome, where comments had always worked, and discovered I didn’t have the add-on installed. So, I installed it—and the same thing happened.

It turns out that the add-on can be disabled just for Blogger.com, which is what I did on Chrome, and it worked. That leaves the add-on functioning to preserve my privacy elsewhere, while allowing me to see comments on my blog (and any others using both Blogger and Disqus).

I never would have known any of this if Firefox hadn’t updated to their new, flashier version. I want to try it as my default browser, but the commenting glitch would have made that impossible. There is, however, one remaining glitch I need to solve.

When I go to my blog on Firefox, I’m not logged in, and I always used to be in older versions of Firefox (and I still am on Chrome). Firefox made a change several updates ago that changed something (no idea what), and now if I access my blog—even if I’m logged into the dashboard on another tab—I’m not logged into my blog. This only matters because after I publish a post I always read the final version, right away or later, and I often notice mistakes I didn’t see before. On Chrome, I just click the “edit post” icon, but on Firefox I have to log in. I could have to repeat that process several times before I’m happy with the post, and on Firefox, re-logging in is annoying.

Still, the thing that I thought would make Firefox unusable for me—a problem with a particular add-on—is now sorted.

Related:
Improved commenting – I talk about the switch when I first made it
How to comment – I provided complete instructions on how to use the Disqus system
Solving commenting problems – the post in which I talked about how to fix a Blogger glitch that prevented the Disqus option from showing up for some people
Unexpected and expected – Not about Disqus as such, but it’s why I permit anonymous comments
The last commenting glitch – this post is about how to work around comments not showing for the most recent post. This is still a problem, and this is the method I tried first when I noticed that comments weren’t appearing on any post with Firefox Quantum.

No comments: