Maybe this will help not only me....
I'm setting up four different user categories so do I need different user table fields or tables? I've got a 'visitor' that needs to be logged in to save a cookie and make the site work in their favor. Three other classes are artists, nonprofits and businesses. These four user categories need to stay in their own turf and I'll do that in the onboarding process.
My 'user' table has the usual name, email and password. I'm following the Xano documentation script:
https://docs.xano.com/building-features/authentication-sign-up-and-log-in
the user table record looks like this:
The function stack looks like the documentation...
so far so good - but we can't see what in the documentation what the user table looks like after signing up :-(
Logging in is where I get lost. The function stack looks like the documentation but we can't see what's going on 'under the hood'. Here in the documentation screenshot. The color themes are different from my screen shots - not sue why.
Here is my login API screenshot:
Check Password.....
precondition....
The password hash creates a different hash in the login than in the signup API. Probably a silly error on my part but I can't see it. :o(
Just my suggestion here. Any documentation that fails to show what is going on in the function stack - 'under the hood' - is incomplete. All that text on the maroon and black fields is REALLY HELPFUL so Xano newbies can understand and learn how to solve problems and what Xano logic and workflow is trying trying to achieve.