Mozilla VPN is currently experiencing an outage. Our team is actively working to resolve the issue. Please check the status page for real-time updates. Thank you for your patience.

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

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

The Plugin Page appears to be broken. It is reporting Shockwave for Director is Outdated Version when it is the same version that is available when I try update

more options

Geez, jumping through hoops to try post this comment. The Firefox Plugin Page is reporting Shockwave for Director 12.0.2.122 is "Out of Date" when it is the same version that is offered when I click "Update."

Shockwave Flash 11.7.700.169 is reported as "Up to Date." I think something may be broken on the Plugin page. That is all I have been trying to say all day.

Regards, Axis

Geez, jumping through hoops to try post this comment. The Firefox Plugin Page is reporting Shockwave for Director 12.0.2.122 is "Out of Date" when it is the same version that is offered when I click "Update." Shockwave Flash 11.7.700.169 is reported as "Up to Date." I think something may be broken on the Plugin page. That is all I have been trying to say all day. Regards, Axis

All Replies (3)

more options

I'm don't know where this should be reported, but...

Based on a file I found fishing around in the cache, it appears the problem is as follows:

The site detects the current version of Shockwave for Director as:

12.0.2r122

In other words, instead of looking for .122 on the end, the page is looking for r122 on the end.

This seems to be a discrepancy between the way Adobe refers to the Shockwave for Director version on its site (with the r) and the way the plugin actually is numbered (with the .). Not sure how this will be sorted out...

more options

Hi jscher2000--

I know what your saying and, yeah, it seems to be as you say...I think.

Actually the Plugin Check page has "Adobe Shockwave for Director Netscape plug-in, version 12.0.2.122" displayed and the Adobe Page I am directed to also says, "Adobe Shockwave Player 12.0.2.122." What you refer to is the Shockwave Flash itself, which is listed on the Plugin Check page as "Shockwave Flash 11.7 r700" as well as "11.7.700.169" in the status column. The Shockwave Flash Player, itself, goes to "Adobe Flash Player 11.7.700.169" on clicking the update link (though the Player itself is listed as "Up to Date.")

I have reported it through the "Firefox Mad Me Sad" page...don't know what else to do but just not worry about it very much...heh.

I just know someone else must be seeing the same thing I am and thought I should make people aware that it is another "weird, unsolved" Plugin Page mystery.

Thanks for your reply jscher2000.

Regards,

Axis

more options

What you refer to is the Shockwave Flash itself

Actually, no. What I'm referring to is a file that Firefox retrieves in the background for each plugin to check the current version. You can't see that file loading and its contents never appear on the page.

If you want to take a peek, type or paste about:cache into the address bar and press Enter. Then follow the link for the disk cache. Note that this can take over a minute to load and lock up your computer while it does.

When it finally loads, you can use the find feature to search for

x-director

to get to the URL of the file retrieved for Shockwave for Director. Click the URL to load the cache detail page, then Ctrl+click the URL there to load the data file in a new tab.

It's all one long line. Search for the following (including the quotation marks:

"status":"latest"

Then click the horizontal scrollbar once and you should see the version information that the plugincheck is looking for.

I did my search immediately after visiting the page, so it was still in the cache. I don't know how long it sticks around. If you don't find it, you could open a separate tab and reload the plugin check page, then search in the cache again.