Closed (fixed)
Project:
Email Change Confirmation
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
18 Aug 2012 at 01:02 UTC
Updated:
8 Nov 2014 at 06:18 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
BassistJimmyJam commentedI ran into the same issue with a different source for user registration that does not provide an email address. Saving the user's profile with a new email address results in the following:
I have attached a patch that resolves the issue.
Comment #2
BassistJimmyJam commentedChanging this to a bug report as I do not believe this is intended behavior.
Comment #4
jaydub commentedThanks for the patch. Makes perfect sense now that external logins/registrations are common with Facebook, Twitter, etc.
Comment #6
klidifia commentedSo this is just bypassing the verification process if there isn't an email to begin with?
Wouldn't it be better to still require validation to ensure that the email is legitimate, and instead perhaps not send an email to the old (non-existant) address?
Comment #7
sfcamil commentedHy,
I use some other modules like User Import an Complete Profile. With User Import the users is created without email and Complete Profile force the user to fill an email when a session is opened. Then this module (Email Confirmation) try to send an email to confirm and that is what I want. But I don't have an OLD email (!) and I have an error when the module try to send email.
What klidifia suggest is better idea.
Any idea how to disable the module to send email to the old (non-existent) email address ?
Thank you all !