View Issue Detail

ID	Project	Category	Submitted / Last Updated
00910	UserSpice	Misc	2020-06-23 20:18:50 / 2020-07-30 17:37:46
Reported	Ray Franklin	Assigned To	Unassigned
Priority	none	Reported	5.1.3
Status	closed	Resolution Version and Commit
Summary	Email verification fails, vericode sent not equal db value
Description	I am consistently seeing an email verification failure on new user registration. Below are the detailed notes. The PNG files I reference in the notes are available in a zip file at https://send.firefox.com/download/90c801b7a822bfa3/#g7Dv1d6GIUGFogVvmsXzEQ Test case: username=support, name=Sup Port, email=support@helioza.com Action/Event Sequence: 1) Register 01JoinForm20200623.png 2) Results 02WelcomeInstructions.png 3) Submitted form OK, email took a few minutes to arrive. 4) Email screen shot 03aVerificationEmail.png 5) Verification Link: https://dev.palindromedary.us/users/verify.php?email=support@helioza.com&amp;vericode=xh9POLu74GJsCNV 6) Clicking verify link displayed Google popup about suspicious link. 7) Google dialog 03bVerificationEmail.png 8) Clicked Proceed. 9) Verification page opened and said verify failed. 10) Screen shot 04aVerificationFailed.png 11) NOTE: vericode in db (uhyBIW2EakABf9f) does not match vericode in link, and email_verified=1 already. 12) Screen shot of phpmyadmin 04bUsersRecord.png 13) Clicked Resend button. 14) Resend form 04cResendVerify.png 15) Resend confirmation 16) Screen shot 04dResendConfirm.png 17) User record changed again, new vericode=NzxLwwtW8Y3b7hT 18) Screen shot phpmyadmin 05UsersRecordAfterResend.png 19) New verification link: https://dev.palindromedary.us/users/verify.php?email=support%40helioza.com&amp;vericode=NzxLwwtW8Y3b7hT 20) Clicking verify link did NOT display Google popup about suspicious link. 21) Verification page opened and said email verified AND unable to verify account 22) Conflicting success/fail messages 06VerifyPassFailed.png At this point I ignored the conflicting messages and was able to login to my new account. I see two issues. 1. The vericode value sent by email does not match what is in the db at that time. 2. The first verification link is not URL-encoded, the email address shows the @ symbol. The second link is URL-encoded. Ray Franklin green@rohswell.com