X
Stuknij, by przejść do witryny w wersji zoptymalizowanej dla urządzeń przenośnych.

Forum pomocy

There is no button labeled "Turn off Blocking for This Site."

Wysłano

I am trying to get content from washingtonpost.com . They need me to disable tracker blocking. The standard help screen (capped below) says to just click the button labeled "Turn off Blocking for This Site." Only trouble is, no such button actually exists on the information popup screen (Clicking the circled 'i'). The popup screen I get looks exactly like the one in the help, except for the missing button. I have tried all the suggestions in other posts and none of them work. I notice I am not the only one with this problem. Is it possible my install of Firefox is corrupted? But nothing else I have noticed is wrong. I am running Firefox quantum 68.0.1 under Ubuntu xcfe.

I am trying to get content from washingtonpost.com . They need me to disable tracker blocking. The standard help screen (capped below) says to just click the button labeled "Turn off Blocking for This Site." Only trouble is, no such button actually exists on the information popup screen (Clicking the circled 'i'). The popup screen I get looks exactly like the one in the help, except for the missing button. I have tried all the suggestions in other posts and none of them work. I notice I am not the only one with this problem. Is it possible my install of Firefox is corrupted? But nothing else I have noticed is wrong. I am running Firefox quantum 68.0.1 under Ubuntu xcfe.
Załączone zrzuty ekranu
Cytuj

Dodatkowe dane o systemie

Aplikacja

  • Identyfikator przeglądarki: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

Więcej informacji

cor-el
  • Top 10 Contributor
  • Moderator
17414 rozwiązań 157300 odpowiedzi

Try to uninstall Adblock Plus. We have seen reports that ABP is still blocking content even when disabled.

You can create a new profile to test if your current profile is causing the problem.

See "Creating a profile":

If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.

Try to uninstall Adblock Plus. We have seen reports that ABP is still blocking content even when disabled. You can create a new profile to test if your current profile is causing the problem. See "Creating a profile": *https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles *http://kb.mozillazine.org/Standard_diagnostic_-_Firefox#Profile_issues If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems. *https://support.mozilla.org/en-US/kb/recovering-important-data-from-an-old-profile
Czy ta odpowiedź okazała się pomocna?
Cytuj

Zadający pytanie

@Fels, thanks for the effort, and thanks for the drink recipe!

@Fels, thanks for the effort, and thanks for the drink recipe!
Czy ta odpowiedź okazała się pomocna?
Cytuj

Zadający pytanie

@cor-el seeing that I have no such problem on any other site, I am henceforth assuming the problem is with washingtonpost.com, and not with Firefox or any of its add-ons. I enjoy the peace that comes with AdBlockPlus, I'm going to keep it for the time being.

@cor-el seeing that I have no such problem on any other site, I am henceforth assuming the problem is with washingtonpost.com, and not with Firefox or any of its add-ons. I enjoy the peace that comes with AdBlockPlus, I'm going to keep it for the time being.
Czy ta odpowiedź okazała się pomocna?
Cytuj
cor-el
  • Top 10 Contributor
  • Moderator
17414 rozwiązań 157300 odpowiedzi

If there is no 'unblock' button in the Control Center 'i' icon drop-down list then this means that content blocking isn't active and there is something else wrong. This could be an extension or changes that you have made to the Firefox default settings that the washingtonpost doesn't like. If it works in a fresh profile then at least you know that it is something in your current profile.

You can try to rename prefs.js in the profile folder to prefsOLD.js to check with settings stored in this file.

If there is no 'unblock' button in the Control Center 'i' icon drop-down list then this means that content blocking isn't active and there is something else wrong. This could be an extension or changes that you have made to the Firefox default settings that the washingtonpost doesn't like. If it works in a fresh profile then at least you know that it is something in your current profile. You can try to rename prefs.js in the profile folder to prefsOLD.js to check with settings stored in this file.
Czy ta odpowiedź okazała się pomocna?
Cytuj
Zadaj pytanie

Aby odpowiadać na posty, musisz zalogować się na swoje konto. Zadaj pytanie, jeśli nie masz jeszcze konta.