With sessions, if someone closes down their browser, it forgets them, so they have to log in again. With cookies you can set a expiry date and it saves people the hassle of logging in, again and again. I store the persons username in the cookie. So if they close down the browser, then load it back up in 2 days time, and wanna change their password. They can do it if they want to.
I hear you thinking, *security risk*?
The user can always logout (expires cookie). And they must know their old password to change to a new one.
Security Question = They have to know their current password to change it. So its kinda like a security question.
To enter in a security question field, every member will have to change their details etc. So that they actually have one, due to the fact that members have signed up already without a secuity question. Testing their current password should fix that problem.
Thanks for your advice, and I appreciate you guys taking a look at the code and suggest what you might change.
ibbo, I'm gonna setup that email thingy you suggest  It's a good idea.
I hope I have gone into everything,
Thnx,
Lothop
|