Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Plugin Check keeps flagging Shockwave for Director despite latest version

  • 3 replies
  • 30 have this problem
  • 35975 views
  • Last reply by Helper7677

more options

When I point Firefox 4.0.1 to the Plugin Check page

<http://www.mozilla.com/en-US/plugincheck/>

It flags the following plugin as outdated:

Shockwave for Director Adobe Shockwave for Director Netscape plug-in, version 11.5.9

However, I have the latest version of Shockwave installed (11.5.9.620) installed. Reinstalling the plugin does not change how the Mozilla Firefox Plugin Check page sees that plugin.

Chosen solution

Adobe Shockwave for Director Netscape plug-in is also known as "Shockwave Player" not to be confused with "Shockwave Flash" which is also known as Adobe Flash. Bad naming conventions by Adobe results in some confusion.

Sorry about the problem with the version number. Version 11.5.9.620 is indeed the latest version, but your plugin does not show the ".620" which is confusing the Plugins Check page. There has been a problem with how Adobe shows the incomplete version number in the past and I thought that was all corrected, but it appears that they have not corrected how it shows in OSX. On my Windows system, the Add-ons > Extensions list and the Plugin Check page shows the full version number (11.5.9.620).

You can always use this page to check and display the full version number on the Adobe site (this page will also test and display the Flash version number): http://www.adobe.com/shockwave/welcome/

You can find the latest version numbers for any Adobe product by reading the most recent security bulletin for each product on this site: http://www.adobe.com/support/security/

Read this answer in context 👍 2

All Replies (3)

more options

Chosen Solution

Adobe Shockwave for Director Netscape plug-in is also known as "Shockwave Player" not to be confused with "Shockwave Flash" which is also known as Adobe Flash. Bad naming conventions by Adobe results in some confusion.

Sorry about the problem with the version number. Version 11.5.9.620 is indeed the latest version, but your plugin does not show the ".620" which is confusing the Plugins Check page. There has been a problem with how Adobe shows the incomplete version number in the past and I thought that was all corrected, but it appears that they have not corrected how it shows in OSX. On my Windows system, the Add-ons > Extensions list and the Plugin Check page shows the full version number (11.5.9.620).

You can always use this page to check and display the full version number on the Adobe site (this page will also test and display the Flash version number): http://www.adobe.com/shockwave/welcome/

You can find the latest version numbers for any Adobe product by reading the most recent security bulletin for each product on this site: http://www.adobe.com/support/security/

more options

Thanks Helper7677.

So, paraphrasing your answer, the Adobe Plugin isn't identifying itself fully (.620), hence the Firefox Plugin Check page thinks my copy of the plugin is out-of-date.

I had checked the Adobe sites you noted, so I was sure I had the latest version. I was thinking this might be a bug in the Plugin Check page, but you've now cleared that up.

Using Property List Editor, I examined the Info.plist within the bundle for this plugin. It identifies the plugin fully in several key-value pairs as 11.5.9r620, but the WebPluginDescription key it has the value:

Adobe Shockwave for Director Netscape plug-in, version 11.5.9

If Firefox is collecting that value, then passing it along to the Plugin Check page, that explains why the Plugin Check page thinks my version is obsolete.

I don't know how Firefox checks for the version information for the plugins it loads, but if it checked the "Bundle versions string, short" key for this plugin it would find the correct version (assuming Adobe always populates that field correctly).

more options

You are welcome.

I do not know the source of the value that the Plugin Check page retrieves.