Closed
Bug 1024323
Opened 11 years ago
Closed 11 years ago
[plugincheck] Adobe Acrobat NPAPI Plug-in update link leads nowhere
Categories
(Websites :: plugins.mozilla.org, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1023718
People
(Reporter: mstanke, Unassigned)
References
()
Details
Attachments
(1 file)
123.79 KB,
image/jpeg
|
Details |
The Update Now button link leads only back to the plugincheck page, the right link should be http://get.adobe.com/reader/ or if there is any common page for Adobe Reader and Adobe Acrobat.
Michal,
your Acrobat does not need to be updated.
I think this is another Duplicate of bug 1023718.
In 1023718 there are links to other bugs about
'Adobe Reader not being detected correctly' on the 'new in 2014 plugincheck'.
See bug 1020133 in the first instance.
Schalk Neethling [:espressive], in bug 956905 comment # 144, said:
> Thanks for the info DJ. I am going to bump the version in the new plugincheck so it
> no longer runs the new code in release 30. Also, the DB has been updated with the
> latest release info for Flash.
Dan Pernokis, who reported bug 1023718, has in bug 1020133 comment # 3
told Schalk Neethling (who has been working on the 'new plugincheck service')
about the redirect.
As I write, the 'Flash result' (bug 1023838) is now correct in Fx 30 and Aurora.
The 'Acrobat result', *this* bug is still not fixed.
Michal,
I also notice, from your screenshot, that your Java might be out of date.
See bug 1023835.
DJ-Leith
Michal,
I meant to also give a link to the most recent
Adobe Security Bulletin
Security Updates available for Adobe Reader and Acrobat
Release date: May 13, 2014
Vulnerability identifier: APSB14-15
http://helpx.adobe.com/security/products/reader/apsb14-15.html
I think your Adobe Reader X (10.1.10) is OK.
DJ-Leith
Reporter | ||
Comment 3•11 years ago
|
||
Thanks DJ-Leith for your exhaustive information. Marking this report as duplicate. And I will also update my Java. ;)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•