Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Unable to update addon

more options

OK, I appreciate that you are trying to help protect people from known vulnerabilities by disabling addons, but you really need to stop disabling the [Update Now] link at the same time.

What is the point of an [Update Now] link, when clicking it doesn't actually update the addon, it just takes you to a page that tells you the addon was disabled because of known vulnerabilities. We know it was disabled because of known vulnerabilities, if we didn't know that, we wouldn't be clicking on the [Update Now] link in the first place.

So far this month, Adobe has had 2 critical vulnerabilities, and while these are not Mozilla's problem, you COULD make the update process actually work, by not disabling the [Update Now] link as well as disabling the addon itself. This means that twice this month, I have had to manually update the addons, a waste of my valuable time when the [Update Now] link should NOT have been disabled.

So my question is, can the developers patch the codebase so that the [Update Now] link does not get disabled, otherwise, what is the point of having an [Update Now] link in the first place?

OK, I appreciate that you are trying to help protect people from known vulnerabilities by disabling addons, but you really need to stop disabling the [Update Now] link at the same time. What is the point of an [Update Now] link, when clicking it doesn't actually update the addon, it just takes you to a page that tells you the addon was disabled because of known vulnerabilities. We know it was disabled because of known vulnerabilities, if we didn't know that, we wouldn't be clicking on the [Update Now] link in the first place. So far this month, Adobe has had 2 critical vulnerabilities, and while these are not Mozilla's problem, you COULD make the update process actually work, by not disabling the [Update Now] link as well as disabling the addon itself. This means that twice this month, I have had to manually update the addons, a waste of my valuable time when the [Update Now] link should NOT have been disabled. So my question is, can the developers patch the codebase so that the [Update Now] link does not get disabled, otherwise, what is the point of having an [Update Now] link in the first place?

Alle antwurden (3)

more options

Plugins such as Flash player, Java, Shockwave, Silverlight etc are not actually installed in Firefox but on system. The updates are done either in the Plugins program or by downloading from the websites.

more options

Do you mean the links on the Plugin Checker website:

https://www.mozilla.org/plugincheck/

Which plugins have links that are not working? Perhaps someone can repair them.

Mine only shows Java, and the link for the button is correct (attached screenshot).

more options

There is a problem with the Shockwave for Director plugin lacking the download URL when I inspect the page data (screen shot attached). But the plugins that the site actually can check look okay.