Closed
Bug 664256
Opened 13 years ago
Closed 13 years ago
Notify someone/somehow on user activation failure
Categories
(support.mozilla.org :: Users and Groups, task)
support.mozilla.org
Users and Groups
Tracking
(Not tracked)
VERIFIED
FIXED
2011-07-19
People
(Reporter: jsocol, Assigned: jsocol)
References
Details
We've gotten sporadic reports of user activation appearing to fail, but actually activating the account. SuMoMo gets 2-3 emails a week about the issue. No one's ever been able to reproduce it, let alone reliably. We don't know why these are failing or how often. We need to get some notification started, email or some other logging of the failure and its reason.
Comment 1•13 years ago
|
||
:james if it will help, i can attach sample emails where SuMoMo users complain about "could not activate my account" error after clicking on an activation link (and logging in as kitsune admin shows the activation error was successful)
Assignee | ||
Comment 2•13 years ago
|
||
I doubt they'd have any information that's helpful for debugging. If you want to share them privately, I can look through it, but I'd rather not publicly attach them here.
Assignee | ||
Comment 3•13 years ago
|
||
Rolling out to 2011-07-05 after the webdev off-site.
Target Milestone: 2011-06-28 → 2011-07-05
Assignee | ||
Updated•13 years ago
|
Target Milestone: 2011-07-05 → 2011-07-12
Assignee | ||
Updated•13 years ago
|
Target Milestone: 2011-07-12 → 2011-07-19
Assignee | ||
Comment 4•13 years ago
|
||
https://github.com/jsocol/kitsune/commit/286691
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 5•13 years ago
|
||
is there a way to force a failure to test this change?
Assignee | ||
Comment 6•13 years ago
|
||
No, no one has been able to reproduce this intentionally, let alone reliably. I have gotten email from allizom, though, with the subject "[Django] User activation failure"
Comment 7•13 years ago
|
||
Verified that Django is sending out user activation error emails on support.allizom.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•