You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The profile email address is currently read from the Contact Main Email. This make some problem because the content manager always need to change the contact and the user email adress.
Expected Behavior
The expect behaviour is the user email is read from the user itself on the profile and is written with the email token to an own entity.
Possible Solutions
Add an email field to EmailConfirmationToken entity.
Read (when exists) and write to this entity instead of the User entity.
The text was updated successfully, but these errors were encountered:
Best solution would that the email address is stored in the EmailConfirmationToken entity instead of ContactMainEmail Entity. In the ProfileType form we would do something like this:
so the email of the user does not get directly mapped to the User entity. From the form you its possible to read then the not mapped value with $form->get('email')->getData() and if it is another value as $user->getEmail(); it can be written in the EmailConfirmationToken and send a confirmation email to the user.
Also it could be configureable if the user can change it's email without confirming it.
Actual Behavior
The profile email address is currently read from the Contact Main Email. This make some problem because the content manager always need to change the contact and the user email adress.
Expected Behavior
The expect behaviour is the user email is read from the user itself on the profile and is written with the email token to an own entity.
Possible Solutions
Add an
email
field toEmailConfirmationToken
entity.Read (when exists) and write to this entity instead of the
User
entity.The text was updated successfully, but these errors were encountered: