Funkcionalnosć tutoho sydła so přez wothladowanske dźěła wobmjezuje, kotrež maja waše dožiwjenje polěpšić. Jeli nastawk waš problem njerozrisuje a chceće prašenje stajić, wobroćće so na naše zhromodźenstwo pomocy, kotrež na to čaka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomhać.

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

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 wotmołwje
  • 26 ma tutón problem
  • 4 napohlady
  • Poslednja wotmołwa wot cor-el

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.

Wšě wotmołwy (2)

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.

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: