Funkcionalnosć toś togo sedła se pśez wótwardowańske źěła wobgranicujo, kótarež maju wašo dožywjenje pólěpšyś. Jolic nastawk waš problem njerozwězujo a cośo pšašanje stajiś, wobrośćo se na našo zgromoźeństwo pomocy, kótarež na to caka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomagaś.

Avatar for Username

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Toś ta nitka jo se archiwěrowała. Pšosym stajśo nowe pšašanje, joli trjebaśo pomoc.

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 wótegronje
  • 26 ma toś ten problem
  • 4 naglědy
  • Slědne wótegrono wót 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.

Wšykne wótegrona (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: