Everything works out quite nice, except one thing I don’t understand…
In tutorial “Creating your first API action - The registration process” there is shown how to select in the 2nd insert execution a return value from the first insert, in order to populate the user_id field in the role table.
When I follow the steps like in the video, and hit the little lightning icon for selecting the value, there are no return values from the first insert. I’m attaching a screenshot.
Hi Hyperbytes!
Thanks for your reply…
But I’m looking for creating the user_id value in the role table.
I believe that password hash is not the correct one.
In your example it should be “insert.identity” and that one is missing on my side.
Absolutely true!
Thanks SO much @Hyperbytes, your tutorials helping me alot getting into Wappler!
I got another question, now I’m hanging at the chapter “Validating the code and confirming the account”.
I went through all of it 5 times now and can’t figure out why I’m receiving an unauthorized notification, when submitting code and e-mail address. I believe it’s the single query, as I have no clue what else it could be. If it was a shell script I’d add a lots of echos in order to troubleshoot, where the issue happens or at least run in debug mode. How can I achieve that in Wappler?
Good morning,
thanks for taking so much care of my issue! I spent another hour now, digging through my code and comparing everything with the video advise again… I’m still getting back an unauthorized notify. Here’s the Chrome Dev/Console output:
So, my register page works, on data input the authcode is sent via E-Mail. I also checked if the mailed code is same as in DB. And I’m getting transfered to the validation page. Here I enter my details. Then immediately I’m receiving that unauthorized.
Hi everybody,
thanks so much for all your help, I’m getting into Wappler very well, but I discovered a serious problem with the SQLite DB…
I tried to creaste those authroles table and it looks like my DB got messed up totally. I can’t apply the changes to the DB nor to data created within, but wappler insists the table is there. Also when trying to delete the table, it says it did but a refresh will show it’s still there, but with a number of changes indicating on the “Apply changes to DB” icon. I restarted my Mac, Wappler and everything, simply no efect. I can’t go on at this point as this table is stuck.
Anybody maybe any ideas how to fix it? I’ll attach a bug report #1695829976736
Hey Hyperbytes!
Yah, in my case I couldn’t fix it after messing it up, so my solution was to pull an older version of that DB file from the git repo.
Cheers!