Bugzilla – Bug 8774
User account created after first wizard screen
Last modified: 2008-08-15 14:46:58 UTC
Should not create user account until they are done with the wizard.
This is all bug 7318: the wizard code is broken in any possible way :-(. When is Devo due? End of august?
One important note: I'll very likely have to disable the "Back" button on the final page. A user who hasn't confirmed his registration yet must not be able to change settings. Otherwise anyone could fake an url to submit changed data with that user's mail address. The registration must be a one time action in one go: when the user is created, that account can't be changed any more until the user logs in.
Thus the final note: "Didn't get the e-mail? We can either resend the e-mail, or you can click Back and change the e-mail address in your registration form." is invalid. You can't go back to change the mail address. Mike - this is an important change. And I'd really like you to be aware of this.
Change 4072 - disable changing an inactive account. User must activate it before he can change mail address etc. QA - please test this asap and very carefully. It's a late change... Thanks
But what happens if I mis-typed my e-mail address? Do I need to go back through the entire reg process again? How can I activate my account if I never get the e-mail? Resending the e-mail to the wrong account doesn't solve the problem. Though it's not a problem, because I can use the browser's back button to go back to the beginning anyway. Are we only worried about SN account fraud, or are there other issues we are trying to solve?
> But what happens if I mis-typed my e-mail address? You start from scratch. > Though it's not a problem, because I can use the browser's back button to go > back to the beginning anyway. Nope. If the account has been created with the wrong mail address, you'll have to start from scratch. > Are we only worried about SN account fraud, or are there other issues we are > trying to solve? What more is needed? We could add a second mail address entry field to reduce the risk of mistyped addresses. Or try to carry around the mail address & password to kind of authenticate without asking again. But I won't do this before we've got a good new plan, the new skin and new wizard code. This code has grown over more than a year and I'm under the impression that even two days before planned launch we still don't know where to go.
Questions: If I enter a Player PIN and the wrong e-mail address does that player get assigned to the incorrect SN account? Or is the PIN attached to the account only after the customer opens the authentication e-mail? Will the customer know to go back and create a new account if they messed up their e-mail, or will they call tech support? If the user enters a bad e-mail address and they can't get the confirmation e-mail does an account get created on the server? Does that account just sit there waiting? How long has the existing behavior been in place?
> If I enter a Player PIN and the wrong e-mail address does that player get > assigned to the incorrect SN account? The assignment is only done when the account is activated. As the mail address is wrong, this very likely will never happen. > Or is the PIN attached to the account only after the customer opens the > authentication e-mail? Exactly. > Will the customer know to go back and create a new account if they messed up > their e-mail, or will they call tech support? Can't speak for the customer. But I would, as would my girlfriend :-). Most I know would probably rather try a new subscription several times before calling support. I guess most of them aren't even aware such a thing as support does exist. > If the user enters a bad e-mail address and they can't get the confirmation > e-mail does an account get created on the server? Does that account just sit > there waiting? AFAIK yes. It will stay there inactive. > How long has the existing behavior been in place? Don't know. I guess from the beginning. Andy might know better. Closing this bug again as these questions aren't bugs, but asking for help to understand the process. Might be worth handling these outside bugzilla.
Verified account isn't created untill after Music Services <NEXT>
This bug is being closed since it was resolved for a version of SqueezeNetwork which is now released! If you are still seeing this bug, please re-open it and we will consider it for a future release.