login validation and verification
Hi can anyone help me in making my validation and verification work for my login page. I have tried reproducing the login condition which I found online and changing that to where the usernames are not equal but it is not showing the error message to tell the user that the username is wrong or the password is wrong. So I was wondering if anyone can hep and give a solution. As well as this is there a way to hide the password (make it look like a traditional password) and translate the username as lower case whatever the user inputs?
Please help, thank you!
- Yasin
Files:
Prototype.zip
Sure - we've done a few things here:
1. There's no need for the 'on tap' + 'set value' event that removes the value of the Input Text Field elements. You can just use a placeholder in the Properties palette.
2. To hide the password, we changed its 'type' in the Properties palette to 'password'.
3. We changed the conditions to check if 0 of the values match the login and the password, instead of ≠ 1.
4. We also separated the actions out into separate interactions, since we want them all to be checked after you click 'Login', rather than only checking one and then stopping when it's validated. Then, we added a 'Hide' action, which updates the message if the user's correctly types in a username/password after the first try.
You mentioned translating the username to lowercase after the user inputs. We could do that, but then it would never match what's entered in the Data Master, because the Data Master usernames are only uppercase.
Sure - we've done a few things here:
1. There's no need for the 'on tap' + 'set value' event that removes the value of the Input Text Field elements. You can just use a placeholder in the Properties palette.
2. To hide the password, we changed its 'type' in the Properties palette to 'password'.
3. We changed the conditions to check if 0 of the values match the login and the password, instead of ≠ 1.
4. We also separated the actions out into separate interactions, since we want them all to be checked after you click 'Login', rather than only checking one and then stopping when it's validated. Then, we added a 'Hide' action, which updates the message if the user's correctly types in a username/password after the first try.
You mentioned translating the username to lowercase after the user inputs. We could do that, but then it would never match what's entered in the Data Master, because the Data Master usernames are only uppercase.
Replies have been locked on this page!