For users logged in to Gravatar, this goes directly to the page where you
change your avatar. For those not logged in, it's a more directed path to
logging in or signing up, compared to the gravatar.com front page. However
it's less clear why you are signing up for a new thing, so maybe that's bad.
Also this link uses HTTPS; it seems we can't get that without the 'en.' prefix.
(imported from commit e03f97ef5ed2ff6593a9b349176da5fd056c4514)
This is now found at servers/puppet/files/mysql/my.cnf . It's identical to the
one we remove here.
(imported from commit fe70529a716842a57058386eaf697a23a6d6251c)
This isn't used by our CSS or Javascript, and we're trying to get rid of the
"zephyr" name.
(imported from commit c3cae24168088eef2bb64944d9a1bd1d8be4b59d)
Previously if you hit /accounts/logout with no ?next=... parameter, you would
see a broken version of index.html missing dynamic content.
(imported from commit d9bca92d1c3c82893524ba69b132d59c48aa34c9)
Validation was happening, but was not preventing sending. We now
just manually call the validation function in compose.finish()
instead of relying on jquery.form's beforeSubmit option.
(imported from commit e094832bf8948f4c6f58cc0d0923bf0fd09db4b1)
External people won't be able to register unless we initiate the action
and send them an email, because the confirmation token generation code
is in the still-protected accounts_home view.
(imported from commit 8985257576d3dff5b0cad9d4b0ae213f18528865)
Here we introduce a new manage.py command, activate_mit, which takes a
number of usernames and sends out emails to the users with instructions on
how to activate their accounts.
(imported from commit f14401b55f915698e83ff27b86434f53e64685f3)
It's possible that the three places we can kill a popover
(body click, Esc, clicking on a new one) should be
refactored to use the same code.
(imported from commit ba7eab480fd2258abfb469c8f1155f29bc63f7f6)
If we have other pages that require login, we might want them to redirect to
the login form. But the root of the site should take you to /accounts/home --
but only after we launch the product.
(imported from commit b5d10e1c908f1ffe1ee68c2689691ca66c896786)
Documentation variously says to disable on the form or on the input box, e.g.:
https://developer.mozilla.org/en-US/docs/How_to_Turn_Off_Form_Autocompletionhttp://msdn.microsoft.com/en-us/library/ms533486%28VS.85%29.aspx
However, at least in Chrome, disabling on the form produces an ugly
"This webpage has disabled autocomplete" message if you try to arrow
down on an input box as if there were suggestions, so I've just put it
on the input element. This still works on recent versions of Safari
and Firefox.
(imported from commit b47f438d6e1d930d7d6871070858c97c6479a0ae)
We weren't listing to compose finish events during reload previously,
which meant that finishing a message was not handled in the same way
as canceling a message.
(imported from commit 4f2576121a8b5354c94348bc2896a2db8c4be000)
Keegan McAllister
Tim Abbott
Waseem Daher
Zev Benjamin
Luke Faraone
Jessica McKellar