Closed (fixed)
Project:
User verification
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
19 Jul 2013 at 21:24 UTC
Updated:
15 Sep 2013 at 13:21 UTC
Hi,
first of all, this module works really awesome!
Im just wondering, if a user for some reasons 'lost' the verification email, how do you regenerate another verification email?
Can i just call _user_verify_send_code($data) to generate and send email token to user?
Thanks,
Joko
Comments
Comment #1
doitDave commentedPrior to finding a way to do that: How do you know a user "lost" his mail? From my experience, they contact you personally. Given that, I (personally) always considered that enough evidence that the user is "real" and just unlocked his account in the backend.
That said, would you still see a usecase for re-sending the code "by click"?
Comment #2
iceous commentedThe problem is, there are many users that are not savvy users where they don't know how to dig through their emails.
Let say, Jack signed up an account, but didn't verify the account that same day, and a month later, he tried to login again.
At this time, he gets "Please verify this account" message, and tries to find his verification email he received a month ago in his mailbox. However, he couldn't find the email ( and let say, he doesn't know how to use search function in the mailbox). Wouldn't it be nice, if Jack can click on a link on the message to regenerate a new verification email?
What do you think?
Comment #3
doitDave commentedOK, I understand that you have set your verification timeout to a value much higher than the initial one I have designed. I did not realize someone would do that ;-)
Well then, it's not that I vote against such a feature. I just did not see the need initially. But, however, _user_verify_send_code() will not work a second time, as it is not just used for mailing, but also for generating the unlock code. So it would be necessary to separate both tasks and have a dedicated "re-send verification code" action. Ideally, this action would integrate with actions API so it could be triggered not just programmatically.
This is a bigger task. It could take me some time, so if someone else wants to contribute, please do so. I am open for patches and/or plugins which add these capabilities. Anyone?
Comment #4
doitDave commentedNB: This will only work within the verification timeout period, as pending accounts get deleted afterwards. After this period, a user would have to sign up again. This behavior is actually part of the core workflow and thus not subject to changes. Just to mention.
Comment #5
iceous commentedThanks for the clarification! Really appreciate it. :)
Comment #6
doitDave commentedIt was less effort than expected. If you install the latest dev snapshot, run update.php and clear your caches (if necessary), you will now find a new mass operation in the user list which resends the code to the selected users. Note that it may take some hours until the changes are in the download package.
Would you please check if that does the trick for you and set the status to rtbc if it does? Thx!
Comment #7
doitDave commentedAs there is no objection at this point, I assume the fix is working.