| 1 |
This module was created to address a missing piece of functionality in
|
| 2 |
the Drupal user system.
|
| 3 |
|
| 4 |
Currently if a user updates their email address there is no
|
| 5 |
confirmation step to ensure that the new email address belongs
|
| 6 |
to the user and is able to receive email.
|
| 7 |
|
| 8 |
In researching this issue I came across a patch to Drupal
|
| 9 |
core to address this issue. The patch is still pending
|
| 10 |
however so I wrote this module borrowing from the code
|
| 11 |
submitted as patches in this issue.
|
| 12 |
|
| 13 |
See http://drupal.org/node/85494 for more information
|
| 14 |
|
| 15 |
This module uses hook_user to intercept when a user is
|
| 16 |
updating their user account. If the email address is
|
| 17 |
being changed then two emails are generated and sent
|
| 18 |
to both the user's original email address and their new
|
| 19 |
email address. The user must click a confirmation link
|
| 20 |
in the email sent to their new email address in order
|
| 21 |
for the change in their account email address to be
|
| 22 |
confirmed. The link in the confirmation email expires
|
| 23 |
after 24 hours.
|
| 24 |
|
| 25 |
The site administrator can configure the subject, from
|
| 26 |
email address, BCC email address if desired and the
|
| 27 |
body of the emails sent to both the user's original
|
| 28 |
email address and their new email address.
|
| 29 |
|
| 30 |
If an email address is changed by a user that has
|
| 31 |
the 'administer users' permission, the email confirmation
|
| 32 |
email is not sent out and the change to the user's
|
| 33 |
information is effective immediately.
|