Quote:
Originally Posted by TheDoc
With a little fancy work you can make the suggested username show up in the input field. Also having very clear error messages based on the different possible issues they could have, clears up some retries. It's minor, but every little bit helps.
|
the real issue is as frozenjag points out the page reloading then they don't realize they have to use a new username and they get screwed again when they submit.. perhaps the IDEAL IDEAL deal would be, give em one chance to make their own username, and if they dupe it, then they get "theirusername_1234" etc.. automatically made for them so they don't have to re-do the username.
Quote:
Originally Posted by FrozenJag
I see the same thing on my paysite.
Ideally NATS should make it to where if a member backs up back to the join form then tries to use the same username again, it shoudl allow him to do so as long as his ip matches up to the first request and the user isnt already a paid member.
Would this be all that hard? Would fix all of these errors and make for more sales I think.
|
Yes but adding IP matching arguments is another database call, I dunno if that's a big deal or not, just playing devil's advoctate, and the way NATS works with usernames, each pre-join submit HAS to be it's own unique event that can't be revisited, they explained it to me, but I forget.
Quote:
Originally Posted by fuzebox
Anyone against letting the member login using their email address and a password?
|
What would happen if he had to redo the username as in the above examples, would have to not use the username, plus NATS won't handle the "@" as a login.