The issue arose, when i tried to fully register another test user. I discovered that if the users email (my own for testing purposes) is entered more thatn once, then it checks the first occurence of this in the database. As the passwords, won't match it won't fully complete registration.
We need to eliminate any ambiguities by a mixture or one of the following;
When the user is applying, we must perform a server side validation check to ensure that the entered user (email) doesn'y already exist in the database.
If email is unique, proceed. If not alert the user to enter a different one as it already exists in the database.
So try/catch block needs to be added, so if email exists, the issue is caught etc....
The issue arose, when i tried to fully register another test user. I discovered that if the users email (my own for testing purposes) is entered more thatn once, then it checks the first occurence of this in the database. As the passwords, won't match it won't fully complete registration.
We need to eliminate any ambiguities by a mixture or one of the following;