After going through the previous videos over again and rebuilding three times, the only thing I can see on my end that is different is on the workflows screen under execute:
That’s correct. In the newer versions, Wappler is hiding the actual POST variables. My understanding is that this is to stop execution of any malicious SQL code injection. You will see the similar SQL query syntax with the conditions.
Have you checked dev console in the browser for any errors?
I’m hunting around on other posts now to see how to resolve, but any additional advice to point me in the right direction is greatly appreciated. If I can provide additional screenshots of specifics, please let me know. At first glance it doesn’t seem to be anything glaring such as the table missing, but it is worth noting that I previously had to delete and re-create the table once before (as part of troubleshooting) . I saved and refreshed everything and redid the execute actions as well afterwards, so I don’t believe it is from that.
Solved! Thank you, Guptast! I tried working through the solutions in the steps above and I think that was part of the problem. The action still wouldn’t work for me. However, I updated Wappler to version 6.0 and my project had all kinds of errors… so, at midnight lol, I decided to start over and rebuilt the whole thing. Third time’s the charm. I never fully figured out the root of the main issue, however I believe the db folder being saved in the incorrect location played a part. When I re-created the project, I saved in the app folder. I also seemed to have some capitalization issues in the form itself when naming the password and email fields of the form (i had updated these from “email” and “password” to"Email" and “Password”. No idea if that has an actual impact, but it seemed to from my testing and was repeatable.
TLDR: problem solved, updated wappler, rebuilt from scratch saving the database file in the app folder from the get-go instead of trying to move later. Thanks all for the help!
Glad to hear that the project is working correctly after re-creating it
The capitalisation of field names in the form would have definitely been one of the issues. If the server action is expecting $_POST.email and the form is submitting $_POST.Email as a post variable, then the API is going to return an error due to a mismatch between the POST variable names.
) but I’m hitting a snag. I’m on my 3rd round through the tutorial trying to see what I missed, but when I made it to video 10, I ran into an issue when testing my form ( Finalising you registration form. (IMPORTANT See note below regarding Password issue) - YouTube)
