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!

Funkcjonalność tej witryny będzie ograniczona w czasie konserwacji. Jeśli artykuł nie rozwiązuje twojego problemu i chcesz zadać pytanie, to nasza społeczność wsparcia jest dostępna na @FirefoxSupport na Twitterze i /r/firefox na Reddicie.

Avatar for Username

Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

Wątek został zarchiwizowany. Jeśli potrzebujesz pomocy, zadaj nowe pytanie.

My plug-in update now button redirects back to the same plug-in check page instead of to the actual download site

DesperateUser
DesperateUser
more options

After updating to 29 when I would check my plug-in status it would either not recognize a plug-in was outdated, or when it did, the update now button would redirect to the plug-in page I was on already. I have been going directly to the sites to update the plug-ins manually. Today I updated to 30, and then after reopening the browser I checked the plug-ins. It said the plug-in for Adobe Acrobat, version 11.0.7.79, was vulnerable. The update now button just redirects to the same page I'm on, again. But, I cannot find any place on adobe to update this plug-in, or even find a version history to confirm the version I have is indeed vulnerable (recently we all went through this with the Java plug-in, when it was the current version although Firefox said it wasn't).

Why is this update now button doing this? Is 11.0.7.79 the latest version? Is there any place on adobe.com that I can go directly for this plug-in? Any help would be appreciated, as this is so frustrating, and I'm concerned about using the browser at all if there is a known vulnerability. TIA.

After updating to 29 when I would check my plug-in status it would either not recognize a plug-in was outdated, or when it did, the update now button would redirect to the plug-in page I was on already. I have been going directly to the sites to update the plug-ins manually. Today I updated to 30, and then after reopening the browser I checked the plug-ins. It said the plug-in for Adobe Acrobat, version 11.0.7.79, was vulnerable. The update now button just redirects to the same page I'm on, again. But, I cannot find any place on adobe to update this plug-in, or even find a version history to confirm the version I have is indeed vulnerable (recently we all went through this with the Java plug-in, when it was the current version although Firefox said it wasn't). Why is this update now button doing this? Is 11.0.7.79 the latest version? Is there any place on adobe.com that I can go directly for this plug-in? Any help would be appreciated, as this is so frustrating, and I'm concerned about using the browser at all if there is a known vulnerability. TIA.

Wszystkie odpowiedzi (2)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 25 Contributor
more options

The plugin check site was updated due to a change in how Firefox reports your installed plugins. (Firefox is less generous with the information now.)

Your version of the plugin is current, as far as I know.

As for the broken button, I see that, too, and I'm not sure what's going on there.

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 25 Contributor
more options

There seems to be a bug in the new site: it is associating the Flash Adobe Acrobat plugin with the Mac version ("Adobe Acrobat NPAPI Plug-in" is the description used on Mac) instead of the Windows version ("Adobe PDF Plug-In For Firefox and Netscape" is the description used on Windows and Linux). As a result, from what I can see, it is not correcting comparing the current plugin version with the site's database. I'm not sure how they're going to fix that, but as far as I can tell, that seems to be the problem as of this moment.

Zmodyfikowany przez jscher2000 - Support Volunteer w dniu