Closed Bug 798531 Opened 13 years ago Closed 13 years ago

String change to "Beta News" on /existing/ and /new/ l10n pages

Categories

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

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jdavis, Unassigned)

References

()

Details

(Whiteboard: u=dev c=l10n p=)

Attachments

(1 file)

mozilla.org/newsletter/existing/ logic needs to be updated so that: If someone is subscribed to the Beta newsletter = they see the Beta newsletter If someone's language is English = they see the Beta newsletter If someone is not subscribed to the Beta newsletter, and their language is not English = they should not see the Beta newsletter. Example user (my testing address): https://www.mozilla.org/es-ES/newsletter/existing/6d24dfa2-388a-4e02-8863-d4033a197cab/ This user should not be able to see the "Noticias Beta" option
Better/easier: Let's leave "beta" on the list for l10n /existing/ pages - and add "(English only)" as part of the title of the Beta newsletter. That means it's a string change on this page rather than technical change.
"Beta News" newsletter title should read "Beta News (English Only)" on both /newsletter/new and /newsletter/existing pages.
Summary: Remove Beta newsletter from /existing/ l10n pages - unless the person is subscribed currently → String change to "Beta News" on /existing/ and /new/ l10n pages
Component: Webdev → General
Product: mozilla.org → www.mozilla.org
Whiteboard: u=dev c=l10n p=
Assignee: malexis → nobody
Priority: -- → P2
No longer need to update /new page - as we're getting rid of it as part of Bedrock migration (Bug 845904). The following newsletters need (English only) added to the end of their title as a precaution: MOZILLA_AND_YOU ABOUT_MOBILE FIREFOX_TIPS FIREFOX_BETA_NEWS AURORA ABOUT_MOZILLA STUDENT_REPS STUDENT_AMBASSADORS (when created) MOZILLA_PHONE APP_DEV AFFILIATES FLICKS
Someone with admin access to basket can make these changes anytime, and they'll show up on /existing and /updated once 845904 (the /existing changes) goes live. Is it worth editing these on the PHP side or should we just keep working on migrating over the newsletter-related pages from there to bedrock?
(In reply to Dan Poirier [:dpoirier] from comment #4) > Someone with admin access to basket can make these changes anytime, and > they'll show up on /existing and /updated once 845904 (the /existing > changes) goes live. Awesome - I just got access from pmac and can update this after a tour next week. > > Is it worth editing these on the PHP side or should we just keep working on > migrating over the newsletter-related pages from there to bedrock? I'm unsure on this as I'm not 100% sure of the complexity of PHP vs. bedrock - malexis can you advise? My 2 cents: It would be nice to have these description on the l10n pages of /existing (since the "English Only" blurb will really only apply to them as a warning).
Looks great with Prod release today 6/5
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: