In past PHP projects 2 years ago I validated a User login before they could be passed on to fill out a 12 field form & submit to the database table for records. I used Wappler documented procedures of 2019-20.
Now in 4.4.5 I am back in a PHP/MySQL application that must run on a client"s server in a folder in the path of his WordPress site. I know the server & my previous apps worked fine.
In 2022 I want to upgrade my methods and use the API Work flows & Security components.
The user login asks for a 7 digit number assigned to the user by our client as the “username” and the “password” is a 5 digit number they will know for their own business region.
The login query will search a preloaded table with the “username” unique numeric value.
AND the “password” Post value for this User’s business. “Select (5 fields) FROM ‘validatelogin’ where username = {{$_Post.Username}} AND password= {{$_Post.Password}}”. Either the unique client record is found or it fails.
In 2019 I modified the User Identity default Wappler login form to just use 2 values as described above.
But in looking at multiple ways to skin this cat now from the different tutorials created over the past couple of years I"m trying to cut to the chase and use the best method in Wappler today.
I don’t want to copy what worked in 2019 for me.
I wasn’t a power user then and am not a power user now with Wappler.
Recently had set up an URL passing variables to be used in a query that was not using a Security provider yet
I want to see the query working with the post values that are not generated until the Submit is used. I’m dithering between using the Submit default form function or to use a javascript click method to pass along variables at the button itself.
@ben has a tutorial with mucho steps https://www.youtube.com/watch?v=3Xrg4EUMRIQ
Before I commit to slavishly following Ben, as I usually have done, I"m doublechecking: looking for any other logical step one, two, etc with Wappler tools reliance.
And, of course, until the user credentials have been verified I don"t want to SET Session values with the first username & password submitted. Only AFTER User verification should I set the Session ID.
I identify at least 3 different methods in this kind of project to take that have me wondering if you experienced Wapplerites have their own semi-sleek Best Practices workflow using Wappler for this – 2 form application – customary login, verify, warning on no success, retry & finally pass through and set the Session after verification.
Or do you recommend that I stick with our main man @ben ?
Last updated: