Hi James, As we talked about earlier this week, I’d like to update the way the modify preferences function works. Currently, when a user clicks 'Modify Preferences' from an email, they can see every newsletter Mozilla offers. This is problematic because some of those newsletters aren’t meant for a mainstream audience (Labs, Aurora, Etc.) Instead, I’d like to only see our major newsletters and then anything they’re subscribed to already. 4 Emails that should always be listed in Modify Preferences: MOZILLA_AND_YOU_FLG ABOUT_MOBILE_FLG FIREFOX_BETA_NEWS_FLG JOIN_MOZILLA_FLG If I were already signed up for other newsletters, they would display here as well. The goal is to give a power subscriber (someone who has everything) one place to manage their preferences, but no overwhelm the casual user with content that isn’t relevant to them. Let me know if this doesn’t make sense or if it’s going to be super complex to implement.
Hi James - Would it make sense to knock this out before Pascal C starts on back end localization? That would give him less to translate. And actually - for international forms - they only need to see Firefox & You. Is that possible an easy switch or complicated?
I think it's rather easy, it's just filtering the forms that are shown on the page. I can do this soon, but probably not until next week. Pascal can only translate the text for Mozilla & You.
Target Milestone: --- → 1.4
Done, please test on dev site: http://www-dev.allizom.org/en-US/newsletter/existing/5129afd0-d084-4a62-89de-8743662b718f/ You should probably sign up with a new user and get the token from Responsys and view the page with it too.
Brilliant. Works perfectly on dev. Thank you!
Sweet! looping in QA just for good measure.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
pushed to production r101294
Whiteboard: r=100950 b=trunk
verified fixed https://www.mozilla.org/en-US/newsletter/existing/index.html
Status: RESOLVED → VERIFIED
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.