Hello!
I have an understanding problem here on the logic of the routines.
When a user registers and with the options of send Validation email and status default Not Validated, the Validation codes is sent to the user. When the admin Validates, the code remains obsolete. The user has a chance to Login without having to insert the Validation code. This simply creates garbage in that table.
Hence, the Status of Validated could be changed by the Admin, but if the user never Validates himself whats the reason of giving a fulll status Validated functionality?
There should be a way to force a user to Validate before the First login which deletes the Validation key.
Hence the Logic should follow that if:::::::::
Should GMail send a registration email out to validate the email a user entered in the demographics section of the signup?
then, it forces the user to enter the Validation code before the first Login, regardless of the status!!!
I have an understanding problem here on the logic of the routines.
When a user registers and with the options of send Validation email and status default Not Validated, the Validation codes is sent to the user. When the admin Validates, the code remains obsolete. The user has a chance to Login without having to insert the Validation code. This simply creates garbage in that table.
Hence, the Status of Validated could be changed by the Admin, but if the user never Validates himself whats the reason of giving a fulll status Validated functionality?
There should be a way to force a user to Validate before the First login which deletes the Validation key.
Hence the Logic should follow that if:::::::::
Should GMail send a registration email out to validate the email a user entered in the demographics section of the signup?
then, it forces the user to enter the Validation code before the first Login, regardless of the status!!!
[BUGREPORT GMail2.0F]VerifyEmail-Problem of logic!