Log in, log out and shake it all about
As I developed the idea of ‘tezztrax’ it became apparent that players may wish to save their games in order to play at a later date. For this, I would need a log in system.
Now, to some, building a log in system is straightforward. Just create a database, add a form and away you go. But as I delved deeper into the subject I quickly realised there was much more to it than that.
First, every player had to have a unique id, otherwise, how would I tell them apart? Secondly, each page had to know whether the player was logged in or not, and if they were, needed to know the status of their current games. Also, logging in isn’t the half of it. You need to verify users via email, have a log out page and allow users to delete their accounts if they wanted.
In all I have ten pages which make up the log in and registration process. They include:
- A registration page for users to create a username and password
- A page confirming a security email has been sent and to which address
- A verification page to securely confirm registration
- A log in page to allow users access to saved games
- A forgotten email page so that users can request to change or update their password
- A reset password page to actually create a new password
- A log out function
- A delete account page for users to remove their account
- A confirm deletion page to warn users what happens where removing their account
- A delete success page to inform users they have successfully deleted their account
This may be too much, but I believe in giving users as much information as possible while navigating the site to minimise any possible confusion.
In order to find out which pages were needed I turned to what has become one of my ‘Go To’ websites, the brilliant Stack Overflow, a forum where experienced coders freely share their knowledge. I find that whatever problem you have, someone has already asked the question, so answers are readily available.