-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The act of resetting a password should automatically mark a user as "verified" #4066
Comments
It makes sense, I'll consider it for the next release. |
I figured I could hack it with: |
The To avoid resaving the record, you can use its before hook, something like: onRecordBeforeConfirmPasswordResetRequest((e) => {
if (e.record) {
e.record.setVerified(true); // this will be saved only if the password reset is successful
}
}) |
I just never see that trigger firing for some reason. |
Never mind, my mistake. Environment isn't set up right. |
Yep, that works. Hooks rock. |
This is implemented in the |
Scenario: The user signs up and never receives a confirmation email. The user clicks on "forgot password" and gets a password reset link, click it, and changes their password. At this point they are still "unverified", though I would argue that ARE verified since they received an email at the given address and clicked on it to verify the address is valid.
This would be the solution to "I didn't get a verification email" -- answer: "just reset your password."
The text was updated successfully, but these errors were encountered: