Fungování této stránky je z důvodu údržby dočasně omezeno. Pokud žádný článek nápovědy nevyřeší váš problém a potřebujete se zeptat na další řešení, napište nám na Twitter @FirefoxSupport nebo Reddit /r/firefox.

Avatar for Username

Prohledat stránky podpory

Vyhněte se podvodům. Za účelem poskytnutí podpory vás nikdy nežádáme, abyste zavolali nebo poslali SMS na nějaké telefonní číslo nebo abyste sdělili své osobní údaje. Jakékoliv podezřelé chování nám prosím nahlaste pomocí odkazu „Nahlásit zneužití“.

Zjistit více

Toto vlákno bylo archivováno. Pokud potřebujete pomoci, založte prosím nový dotaz.

Every time I start up Firefox, it checks for plugin updates. All my plugins are up to date, but it continues to load the plugin site. How do I make it stop?

  • 2 odpovědi
  • 26 má tento problém
  • 4 zobrazení
  • Poslední odpověď od cor-el

srl1992
srl1992
more options

Starting on Fri. 6/10/11, every time I start up Firefox 3.6.17, it loads the plugin update site. Initially, it said my Adobe reader plugin was out of date. Therefore I updated that plugin, yet that did not fix the problem. So I was finally forced to disable the plugin. After doing this, the plugin updates check still runs every time I start FF. However, they all come back up to date.

So my question is how do you make this plugin update check stop running. I had made no changes to firefox prior to this.

Starting on Fri. 6/10/11, every time I start up Firefox 3.6.17, it loads the plugin update site. Initially, it said my Adobe reader plugin was out of date. Therefore I updated that plugin, yet that did not fix the problem. So I was finally forced to disable the plugin. After doing this, the plugin updates check still runs every time I start FF. However, they all come back up to date. So my question is how do you make this plugin update check stop running. I had made no changes to firefox prior to this.

Všechny odpovědi (2)

the-edmeister
the-edmeister
  • Moderator
more options

There's a fault with the blocklist.xml file which was updated on Friday, it should be fixed on Monday and you should get the updated file on Monday or Tuesday.

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

You can fix this problem with forcing the file blocklist.xml to update.

That update will remove the severity="0" flags in the file that cause the problems.

See: