Needs review
Project:
Email Change Confirmation
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
6 Aug 2014 at 23:22 UTC
Updated:
27 Aug 2019 at 14:40 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
djac commentedComment #2
purushotam.rai commentedI feel we should make it more generic not just LDAP, we definitely need a workaround on this.
Comment #3
ludo.rI think the module should indeed ask other modules wether the email change should be handled or not.
By implementing a new hook.
Alternatively, you can add following value in the edit array, using
hook_form_alter()orhook_user_presave()(this one should be fired before theemail_confirrm_user_presave()):If this value is set to TRUE, email_confirrm_user_presave() won't do anything.
This is the approach I just did.
But email_confirm module should defintely implement a specific hook.