X
點擊此處開啟此網站的行動版。

技術支援討論區

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

已張貼

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.
附加的畫面擷圖
引用

額外的系統細節

應用程式

  • User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

更多資訊

cor-el
  • Top 10 Contributor
  • Moderator
17424 個解決方法 157436 個答案

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
這篇文章有幫助嗎?
引用

提出問題者

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

@Fels, thanks for the effort, and thanks for the drink recipe!
這篇文章有幫助嗎?
引用

提出問題者

@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.
這篇文章有幫助嗎?
引用
cor-el
  • Top 10 Contributor
  • Moderator
17424 個解決方法 157436 個答案

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.
這篇文章有幫助嗎?
引用
問個問題

如果您還沒有帳號,您必須先 登入您的帳號 來回覆文章。請 開始一個新問題