Split Login and Register into two parts

[Martii]

• Something @sizzlemctwizzle suggested he might want from an idea he had with a little twist from myself. I think this covers what you are describing plus a little extra.

NOTES:

• There can be more to do with this if needed.
• This shows the sanitized name as indicated in a previous discussion about it. Added a note about it in the CAUTION alert.
• If an existing user needs to change their auth method, and they are not already logged in with their preferred, just page back from whatever auth page there is (say GH's login prompt) and it will give the register screen... otherwise use the Preferences to initially add an alternate authentication to an existing account.

Applies to:

• Allow username change #233
• https://openuserjs.org/discuss/Remove_my_account.#comment-15aa269078a

[Martii]

@sizzlemctwizzle
This should alleviate #233 from being handled by Admin+ totally (e.g. imho it can be closed and I shouldn't have to do that any more in a DB migration). A new user gets a chance to see/preview what username they are going to end up with and have an option to change it. This also isolates the registration attachment to a separate screen to eliminate that confusion. The wording fits within the guidelines that you mentioned to me earlier.

[Martii]

If you still want an ajax listener it is preferred to be handled before calling out the form/route request using the not-existing-yet User.search client-side API that you mentioned. I advise against a real time search like Groups and that many DB lookups could get messy (for this case something like User.findOne client side API and a cleanfilename routine is recommended on "Sign-In" which might be renamed to "Next" soon... if you feel the host can handle it then make it live but may have consequences).

This minimal amount of JavaScript won't hurt those that don't like enabling JavaScript by default... but could be abused still... they'll just need to figure it out the current existing method... that's already in place.

---

If you still don't want to split the screens into two, as is, then let me know an I'll remove the mustache conditionals... but the biggest confusion I've encountered from others is having two input boxes with the same username (sanitized or not) on the same screen. Usually they type in their email address next to the auth drop list/register button after they've already chosen a username in the upper input... that's where it gets blech. Slowing registration options down should ease this. Flipping auths is still possible when there's a development issue but just a little more obfuscated than it already is. The needs of the many outweigh the needs of the few... in this case. ;) :)