Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Ko tenda hembiapoite sa’ivéta oñemba’apokuévo hese hembiapo porãve hag̃ua. Peteĩ jehaipyre nomoĩporãiramo ne apañuái ha eporanduséramo, roguerekohína ore nepytyvõ rekoha ikatútava ndeykeko @FirefoxSupport Twitter-pe ha avei /r/firefox Reddit-pe.

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

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 Mbohovái
  • 26 oguereko ko apañuãi
  • 4 Hecha
  • Mbohovái ipaháva 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.

Opaite Mbohovái (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: