Closed
Bug 616365
Opened 15 years ago
Closed 15 years ago
Update the AAQ process to reflect confirming users, not questions
Categories
(support.mozilla.org :: Questions, task, P3)
support.mozilla.org
Questions
Tracking
(Not tracked)
VERIFIED
FIXED
2.4.1
People
(Reporter: paulc, Assigned: paulc)
References
Details
Now that we're registering users through kitsune, AAQ can benefit from the confirmation step to actually be on _users_ as opposed to _questions.
We need to update the text and email accordingly to let the user now that:
* They need to confirm their email in order for their question to show up
* They will only be able to post this one question until they confirm their email
* We should probably log them in during the confirmation step as well, so they can ask other questions/do whatever.
This also means removing the confirmation step for already-active users, making that experience better for them. Could be a separate bug :)
Comment 1•15 years ago
|
||
This is a "nice to have" but not necessary for 2.4.
(In reply to comment #0)
> * We should probably log them in during the confirmation step as well, so they
> can ask other questions/do whatever.
I'm not even sure we can do that the way Django authenticates people, but showing a login form on the successful-confirmation page makes me feel safer anyway.
> This also means removing the confirmation step for already-active users, making
> that experience better for them. Could be a separate bug :)
That's trivially part of this. We strip out the code that sends the question confirmation and eventually remove the columns as well, and only show questions where question.creator.is_active = True.
Priority: P2 → P3
| Assignee | ||
Comment 2•15 years ago
|
||
(In reply to comment #1)
>
> I'm not even sure we can do that the way Django authenticates people, but
> showing a login form on the successful-confirmation page makes me feel safer
> anyway.
Yeah. Probably safer and also... possible!
Comment 3•15 years ago
|
||
Let's do this over time to make sure we handle unconfirmed questions correctly.
Target Milestone: 2.4 → 2.4.1
| Assignee | ||
Updated•15 years ago
|
Assignee: nobody → paulc
| Assignee | ||
Comment 4•15 years ago
|
||
https://github.com/jsocol/kitsune/commit/43760e1d53afd3998c37629023b8c618e1f4adda
(In reply to comment #3)
> Let's do this over time to make sure we handle unconfirmed questions correctly.
Yep, so, for QA, here's what's happening now:
* Only _new_ questions for active users show up directly.
* Old unconfirmed questions still need to be confirmed through the same process as before
* And inactive users asking new questions will be sent the same email they are sent on registration, and taken to a page which tells them to confirm their email before their question will appear in the list.
Please don't hesitate to ask if you have questions about testing this.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Comment 5•15 years ago
|
||
Verified all except old confirmed questions- which will be done after the prod data dump
Comment 6•15 years ago
|
||
Verified old confirmed questions after prod data dump- bring up confirmation as before, questions added to /questions
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•