Hi everyone!.
I wanna know your opinion about implementing email confirmation considering this:
customer.pre_create event, the user must be disabled and a confirmation token should be generated (use the same field used in password request).confirmAction which use the confirmation token as parameter, the action validate the token and enable the user and set the confirmationToken to null.ConfirmAction should redirect to login if the token is valid and dispatch pre_confirm and post_confirm events.user is created with disabled state, the AutoLoginListener is no longer works, so should be deleted.prepareResetPasswordRequest method on the UserController must verify the status of the user for prevent the execution when the user is disabled (show the flash message sylius.user.email.not_exist for example)Actually, I'd like to have this toggleable. So basically being able to easily enable/disable the listeners responsible for autologin and confirmation token generation/email + disabling user. Just like FOSUserBundle is doing it, IIRC. Thoughts?
Any progress here? or defined workflow for this?
Currently we're implementing email verification. The workflow is the following:
And also a possibility to resend confirmation email.
I would suggest to wait for this functionality and then we can add configurable option to disable user account at default and enable it after verification. It will only require to disable autologin listener, disable UserRegistrationFormSubscriber which enables user on registration form submit and enable user after the verification.
@michalmarcinkowski 馃憤 ... I will wait then :D
@michalmarcinkowski do you have any news about this feature? At what stage it is now?
The email verification feature is already merged (see #5029), so now this feature should be easy to add.
We don't plan to implement this feature soon, but if anyone from community is willing to work on it, we will be happy to help 馃槈
Most helpful comment
The email verification feature is already merged (see #5029), so now this feature should be easy to add.
We don't plan to implement this feature soon, but if anyone from community is willing to work on it, we will be happy to help 馃槈