Closed Bug 631039 Opened 14 years ago Closed 14 years ago

Email opt-in on check plug-in page

Categories

(www.mozilla.org :: General, defect, P3)

x86
macOS
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: wbowden, Assigned: jlong)

References

()

Details

Attachments

(2 files)

I noticed that the U.S. version of the Check Your Plugins page doesn’t have an email opt-in. This would be a great place to add an option to sign up. Ideally, I’d love to place an optin underneath “Need Help”. At a minimum, would it be possible to add our standard footer? If we can go beneath Need Help, we can tailor our copy to highlight the fact that we have plugin information in our newsletter. See suggested copy below and screen shot of page I’m referring to with a quick sketch. COPY: Get Mozilla News Subscribe to monthly email updates and keep current with Mozilla news, including details about new and innovative plug-ins! URL - http://www.mozilla.com/en-US/plugincheck/ Thanks, Winston
Laura, should we make this a website bug? Seems like it's straightforward enough we could skip straight to silverorange and hopefully get it into 1.3 (although that release is getting pretty crowded).
Yes - I think that's fine. Moving to 1.3 website bug. John - Can you take a look at the proposed copy and finalize it?
Assignee: tshahian → nobody
Component: Design → www.mozilla.com
Product: Marketing → Websites
QA Contact: design → www-mozilla-com
Target Milestone: --- → 1.3
Here's my suggested copy: Get Mozilla News * Find out what's happening with Firefox, including the latest plugin info. _Subscribe to the monthly newsletter_. In terms of functionality, I assume this link would take you to the main email signup page? (vs having the sign-up take place directly on this page, that is) If that's not correct, we may want to set this up a little differently.
Copy looks great. Thanks. If it's possible, I'd prefer an implementation that's similar to the newest versions you rolled out that allows the visitor to opt-in on the page vs. taking them to another URL. That's been so successful on the other pages, I'd like to use that optin method whenever possible.
Assignee: nobody → steven
Target Milestone: 1.3 → 1.4
Target Milestone: 1.4 → 1.5
Target Milestone: 1.5 → 2.0
Target Milestone: 2.0 → 2.1
Assignee: steven → jlong
Target Milestone: 2.1 → 2.2
Priority: -- → P3
Target Milestone: 2.2 → 2.4
Winston, how do this look? Check the URL of the bug (points to trunk).
Awesome! Looks great. Responsys integration looks good too. Did a test and I was added.
Also - quick note - if we localize this page, for the time being, the newsletter opt-in should NOT be included in the localizations.
Cool! Marking qawanted, but not closing until I talk to Pascal to see how to communicate the requirement in comment 8.
Keywords: qawanted
Attached image screenshot
James can you change the button color? I think a lot of users might miss it
Target Milestone: 2.4 → 2.5
(In reply to comment #10) > Created attachment 531384 [details] > screenshot > > James can you change the button color? I think a lot of users might miss it What browser was that in? I have a more styled button, so that must be in an older browser.
fixed grey background in r88663
Status: NEW → RESOLVED
Closed: 14 years ago
Keywords: qawanted
Resolution: --- → FIXED
Please open (In reply to comment #13) > keywords: qawanted => ; status: RESOLVED => REOPENED; resolution: FIXED => > reopening due to 404 error on page Please open a new bug if this is important, as it's completely unrelated to this bug. I suspect that's just part of the "check plugin" process, if it throws a 404 it's an unknown plugin or something. Someone who is remotely familiar to the check plugin functionality should be on the one to fix it.
Status: REOPENED → RESOLVED
Closed: 14 years ago14 years ago
Resolution: --- → FIXED
(In reply to comment #14) > Please open (In reply to comment #13) > > keywords: qawanted => ; status: RESOLVED => REOPENED; resolution: FIXED => > > reopening due to 404 error on page > > Please open a new bug if this is important, as it's completely unrelated to > this bug. > > I suspect that's just part of the "check plugin" process, if it throws a 404 > it's an unknown plugin or something. Someone who is remotely familiar to the > check plugin functionality should be on the one to fix it. qa-verified-trunk http://www-trunk.stage.mozilla.com/en-US/plugincheck/ email form.
pushed to production r89092
Status: RESOLVED → VERIFIED
Component: www.mozilla.org/firefox → www.mozilla.org
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: