Closed
Bug 788473
Opened 12 years ago
Closed 12 years ago
Add id and ru newsletter to the list of newsletters with double confirmation on signup
Categories
(www.mozilla.org :: General, defect)
www.mozilla.org
General
Tracking
(Not tracked)
RESOLVED
FIXED
Future
People
(Reporter: rik, Assigned: rik)
References
Details
(Whiteboard: u=dev c=email p=1)
No description provided.
Assignee | ||
Comment 1•12 years ago
|
||
Pull Request is at https://github.com/mozilla/basket/pull/3
Assignee | ||
Comment 2•12 years ago
|
||
Jess: In bug 745011 comment 8, you mention that the key for RU should be ru_confirmation_email_2. That's a difference with other keys. You can see the current list at https://github.com/mozilla/basket/blob/master/apps/news/tasks.py#L25 Can you confirm we really want this "_2" ?
Comment 4•12 years ago
|
||
Hi Anthony, I believe what Jess mentioned in 745011 is correct. The external key for that particular email does contain the _2. It reads ru_confirmation_email_2
Updated•12 years ago
|
Whiteboard: u=dev c=email
Target Milestone: --- → Future
Comment 5•12 years ago
|
||
"ru_confirmation_email_2" is the correct key for the Russian newsletter welcome email. Can you give a timeline ETA for implementation? Thanks! Jess
Comment 6•12 years ago
|
||
Hey Anthony, Welcome back from vacation! I hope you had a lovely week. Checking in on this Bug for Q3: does Sept 27th for implementation sound achievable?
Assignee | ||
Comment 7•12 years ago
|
||
The code is ready. Opened bug 792098 to get this deployed.
Comment 8•12 years ago
|
||
Anthony, can you let me know when the links are live on Stage? I'd like to run them through tests before they go live. Thank you.
Assignee | ||
Updated•12 years ago
|
Assignee | ||
Updated•12 years ago
|
Whiteboard: u=dev c=email → u=dev c=email p=1
Assignee | ||
Comment 9•12 years ago
|
||
Closing as the backend work has been done. We now have to deploy the content of bug 745011 and bug 745032 after tests are positive.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•