Closed Bug 1226467 Opened 9 years ago Closed 2 years ago

Shockwave for Director 12.2.0.160 "Update now" link points to security advisory instead of update

Categories

(Plugin Check Graveyard :: UI, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: FredMcD, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0
Build ID: 20151029151421

Steps to reproduce:

I was checking my plugins, and found that my Shockwave for Director 12.2.0.16
was blocked. In the notice is an "Update Now" link.


Actual results:

The link did not help me to update the plugin. Instead, it sent me to
https://blocklist.addons.mozilla.org/en-US/firefox/blocked/p1054
Schalk, this looks like bug 1060990 but for Director instead of Flash.
Component: Untriaged → UI
Flags: needinfo?(schalk.neethling.bugs)
Product: Firefox → Plugin Check
Summary: Shockwave for Director 12.2.0.160 → Shockwave for Director 12.2.0.160 "Update now" link points to security advisory instead of update
Version: 42 Branch → unspecified
(In reply to FredMcD from comment #0)
> User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0) Gecko/20100101
> Firefox/42.0
> Build ID: 20151029151421
> 
> Steps to reproduce:
> 
> I was checking my plugins, and found that my Shockwave for Director 12.2.0.16
> was blocked. In the notice is an "Update Now" link.
> 
> 
> Actual results:
> 
> The link did not help me to update the plugin. Instead, it sent me to
> https://blocklist.addons.mozilla.org/en-US/firefox/blocked/p1054

I will have to have a look at the URL people are pointed to here but, when something is on the blocklist, that is the correct page to be sent. Can you copy and paste the link the button is sending you to?

If it is different from the one in your comment. Thanks!
Flags: needinfo?(schalk.neethling.bugs)
I have already updated my software. Sorry.

Shockwave is no longer supported

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.