* When someone goes to the /existing page with an invalid token or no
token, redirect them to a recovery page
* On the recovery page, they can enter their email address and we'll
send them a message containing a valid link to manage their subscriptions.
* If the email is not known, we tell them to check for typos or go sign up.
In the headline on the /newsletter page, turn off the special styling
of the span tag. We'd rather just remove the span tag from the text,
but that would invalidate all the existing translations.
The issue was that in the header 'Read all about it in our
<span>newsletter</span>', the <span> and </span> each were causing a
line break. In languages like Indonesian where the word order was
changed, e.g.:
Baca selengkapnya di <span>nawala</span> kami
this was breaking the header up into three short lines.
It turned out that header spans were being styled in newsletter.less
as "display: block". Getting rid of that solves the problem.
The styling sheet on /newsletter/existing ws messed up - the
descriptions were all bolded and the newsletter titles were small.
Reverted styling of the TH part of the table to what it was in an
earlier version of newsletter.less. No way to tell what happened
to it due to rebasing on the original branch.
- Create newsletter app and move hacks.mozilla.org.html there
- Set up to display Django messages to the user.
- Make displaying most of the information on the page conditional on having a formset, so we can still use the same template when some error occurs in processing.
- Handle errors by displaying translated messages to the user. Also use Playdoh logging to log errors and debug information.
- If no token given, or token is invalid, let user supply an email
address and sign up for newsletters.
Alex Gibson
Dan Poirier
Steven Garrity