The plugin for the Classic version is 3.2205, according to what the plugin check is showing me. I have the current Classic version installed, as I ran the plugin check yesterday, saw Reader was out of date, poked around, and saw what was going on with the new Acrobat Reader DC versions. The version numbers are different depending on what track's installed - the current Classic version is 2015.006.30033, while the current Continuous version is 2015.007.20033 (not sure on the hidden change list field version - I did Help | About, but it didn't show that in my install). Check for updates in Reader XI won't find the new version because of the name/version number change. The new versions of Reader are called Adobe Acrobat Reader DC, and they have two different release tracks, Classic and Continuous (see for discussions of the new tracks). The 'JSON List' method has "unknown" plugins reported - GOOD.Īctually, Adobe has released not one, but two new versions of Reader. The 'JSON List' method REQUIRES "plugins.enumerable_names" set to "*"ī. See my comment in bug 1102198 comment # 3, where STAGE and LIVE have different results.Ī. On, in bug 1102198 comment # 2 there is a Bedrock pull request mentioned. Just one important note, please keep feedback here > Improvements to this has landed on production. > NO tests are done and NO 'results are shown'.īug 1020133 "Improve Adobe Acrobat plugin reporting". > Now, because NO plugins are being enumerated, Modify "plugins.enumerable_names" to "" (empty string). ONLY Flash will be 'tested and reported on'. > to "Shockwave" which means 'test my Flash plugin' in this context. > from the default "*" which means 'enumerate all plugins' I also reverified steps 4 to 8 (on en-US),Ĭlearing all cookies and cache each time. I cleared all cookies and repeated (using ++ to reload without cache).
ADOBE READER 11.0.11 MAC WINDOWS
Test bug 1084537 "Flash sometimes displayed as up to date whilst vulnerable, on Windows 7" I have deliberately NOT updated Flash, so that I have a vulnerable version to "Plugincheck-Fx-37-0-1-Reader-WRONG-Flash-Correct-.png" > If you 'click the link' "Check to see if your plugins are up to date". > in "about:addons", at the top of the "Plugins" Tab. > The way a 'User is expected to do this' is: > have been on 'test Profiles that have been in use for months'. > All my 'normal tests', previously reported in Bugzilla, > I did steps 1-3 today to eliminate any of my Addons from confounding the tests. > Repeat 2 and 3 several times (to finish 'first run / fresh Firefox profile'). > As the Plugins are 'machine wide' I have several that I can test.
ADOBE READER 11.0.11 MAC WINDOWS 7
> Windows 7 64bit OS, Firefox 37 Release (32bit), en-GB. I have used a new Profile, on Firefox 37.0.1 Release, to do tests without any Addons.
Plugincheck-Fx-37-0-1-Reader-WRONG-Flash-Correct-.png The screenshot (above) also shows what happens when I try and use
I hope this is not bug 1020133 "Improve Adobe Acrobat plugin reporting"īug 1154397 (to add Flash 17.0.0.169 to the Plugincheck Database on )īug 1153448 "L10N Plugincheck, locale missing, en-GB has become en-US" I can not find a bug in Bugzilla to add a new version of 'Adobe Reader' In Adobe Reader, Help, "Check for updates."
ĪFAICT, Adobe have not released a new version.Īlso does not have a Security Bulletin for Reader in April 2015. Yesterday,, Adobe Reader 11.0.10.32 was correctly shown as "Up to Date". Details "Plugincheck-Fx-39-Reader-WRONG-Flash-Correct-.png" Plugincheck-Fx-39-Reader-WRONG-Flash-Correct-.png
0 kommentar(er)
