Mozilla Destek’te Ara

Destek dolandırıcılığından kaçının. Mozilla sizden asla bir telefon numarasını aramanızı, mesaj göndermenizi veya kişisel bilgilerinizi paylaşmanızı istemez. Şüpheli durumları “Kötüye kullanım bildir” seçeneğini kullanarak bildirebilirsiniz.

Daha Fazlasını Öğren

Does anyone know how to fix the "fail to load" comments problem (WSJ online)?

  • 19 yanıt
  • 3 kişi bu sorunu yaşıyor
  • 128 gösterim
  • Son yanıtı yazan: humble_62

more options

Subscribers of the Journal can read and write comments. Since a week ago, the comments section fails to load. First I reported this problem to the editors but they are unaware of it. Meanwhile I have found that it seems to directly related to the Firefox Quantum (57.0.4 64-bit) browser. In fact with the older Firefox 32-bit version (running on an old computer), Google Chrome or Internet Explorer the comments sections works perfectly.

Help to fix this problem will be highly appreciated.

Subscribers of the Journal can read and write comments. Since a week ago, the comments section fails to load. First I reported this problem to the editors but they are unaware of it. Meanwhile I have found that it seems to directly related to the Firefox Quantum (57.0.4 64-bit) browser. In fact with the older Firefox 32-bit version (running on an old computer), Google Chrome or Internet Explorer the comments sections works perfectly. Help to fix this problem will be highly appreciated.

Seçilen çözüm

humble_62 said

Seems to me that the Quantum browser deems this module unsafe and therefore blocks the loading.

Well, there's no message pointing in that direction, for example, no reference to Content Security Protection rules or mixed active content blocking.

Perhaps there is some other setting I'm not thinking of.

One other thing you could try while you wait for any authoritative explanation is to try a fresh Firefox profile. This will exit your current session, so probably best to complete any ongoing work first.

New Profile Test

This takes about 3 minutes, plus the time to test the site.

Inside Firefox, type or paste about:profiles in the address bar and press Enter/Return to load it.

Click the Create a New Profile button, then click Next. Assign a name like Jan2018, ignore the option to relocate the profile folder, and click the Finish button.

After creating the profile, scroll down to it and click the Set as default profile button below that profile, then scroll back up and click the Restart normally button. (There are some other buttons, but please ignore them.)

Firefox should exit and then start up using the new profile, which will just look brand new. If you are asked to enable any add-ons, just ignore that for the time being.

Does WSJ commenting work in the new profile?

When you are done with the experiment, open the about:profiles page again, click the Set as default profile button for your normal profile, then click the Restart normally button to get back to it.

Bu yanıtı konu içinde okuyun 👍 2

Tüm Yanıtlar (19)

more options

Links so those whom subscribe like you can see what your saying?

more options

Make sure you are not blocking content.

Start Firefox in Safe Mode {web link} by holding down the <Shift> (Mac=Options) key, and then starting Firefox.

A small dialog should appear. Click Start In Safe Mode (not Refresh). Is the problem still there?

more options

Thank you FredMcD. Shall try the Safe Mode as you suggest and revert later.

more options

@FredMcD. Just tried the Safe Mode. Unfortunately, the result is the same. Thanks anyway.

more options

WestEnd said

Links so those whom subscribe like you can see what your saying?
more options

@WestEnd. Yes, I want everybody to be able to see this but not sure what you mean by "Links". Possibly I missed something. In case, please let me know. Thank you.

more options

A post was flagged as Solved Problem. If the problem is not solved, please remove that flag. If you don’t, others that can help may not read this post.

Go to that message, and use the Undo link to its right.


Please provide public link(s) (no password) that we can check out. No Personal Information Please !

more options

WSJ has a paywall, but you often can access articles shared on social media without having an account. I don't think that applies to this forum!

more options

One common issue recently is more embedded content blocked by the Tracking Protection feature. If you notice a "shield" icon toward the left end of the address bar while you're viewing a page with this problem, try clicking that and making an exception. More info on this feature: What happened to Tracking Protection?.

more options

Do you see any messages related to this issue in the Web Console?

  • "3-bar" menu button or Tools -> Web Developer
more options

Thanks to all for your replies.

As suggested by cor-el, I opened the console from the page where comments cannot load. My BASIC programming experience is not helpful to understand this. Could you have a look at the attached screenshot and tell me about your findings? Thank you.

more options

The last message -- loading failed for the LifeFyre script -- is the one most directly related to commenting. But why did it fail, is the question. Usually it would be a content blocker, either the built-in Tracking Protection feature, or an add-on. If you get that same error in Firefox's Safe Mode, and you do not see the "shield" icon for Tracking Protection, it's a mystery.

more options

@jscher2000. Good point. Had read earlier that this forum platform is indeed run by the LifeFyre script. it is a mystery, as you say - there is no shield icon in Safe Mode. Seems to me that the Quantum browser deems this module unsafe and therefore blocks the loading. To find out where and why this happens, presumably we need the help of someone who is totally familiar with the program code. Thank you for your input.

more options

Seçilen çözüm

humble_62 said

Seems to me that the Quantum browser deems this module unsafe and therefore blocks the loading.

Well, there's no message pointing in that direction, for example, no reference to Content Security Protection rules or mixed active content blocking.

Perhaps there is some other setting I'm not thinking of.

One other thing you could try while you wait for any authoritative explanation is to try a fresh Firefox profile. This will exit your current session, so probably best to complete any ongoing work first.

New Profile Test

This takes about 3 minutes, plus the time to test the site.

Inside Firefox, type or paste about:profiles in the address bar and press Enter/Return to load it.

Click the Create a New Profile button, then click Next. Assign a name like Jan2018, ignore the option to relocate the profile folder, and click the Finish button.

After creating the profile, scroll down to it and click the Set as default profile button below that profile, then scroll back up and click the Restart normally button. (There are some other buttons, but please ignore them.)

Firefox should exit and then start up using the new profile, which will just look brand new. If you are asked to enable any add-ons, just ignore that for the time being.

Does WSJ commenting work in the new profile?

When you are done with the experiment, open the about:profiles page again, click the Set as default profile button for your normal profile, then click the Restart normally button to get back to it.

more options

Excellent suggestion! Thank you. Shall try this over the weekend and let you know.

more options

Did you try to open one or more of the scripts that fail to load via the location/address bar to see if that give a better error message?

more options

@jscher2000. Thank you for the detailed description of this test. With the blank profile the comments indeed loaded immediately! So you correctly suspected that a cookie (or similar) caused this problem. Next step will be easy - backup the saved bookmarks and then import it with the new profile running. Shall keep your post for future reference. Thanks again.

more options

I believe the problem has nothing to do with Mozilla. I experience it with Chrome and Edge as well. I think it is just DJI's weak IT infrastructure.

more options

@mdash,

You are right - the problem was not related to Mozilla. The readers' comments are running on a separate system and the WSJ editors were not aware of this problem. While they did not care to respond to my complaint, apparently someone has done some work on it. Presently, comments are loading instantly with the Quantum browser.