Page MenuHomePhabricator

ConfirmEmailComplete fires again if you confirm an already-confirmed email
Closed, ResolvedPublic


None of Special:ConfirmEmail, User::newFromConfirmationCode, and User::confirmEmail check if an email is already confirmed. newFromConfirmationCode just checks if it's a valid non-expired code, but using a code does not expire it.

It's fine not to show an error for double confirmations, but the hook should not fire twice. I don't think setEmailAuthenticationTimestamp should be called again either, so my patch will avoid doing so.

Version: 1.21.x
Severity: normal



Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 1:26 AM
bzimport set Reference to bz46655.

Proposed fix at

It calls isEmailConfirmed to see if they're already confirmed. If so, it returns true without doing anything.

This does mean the EmailConfirmed hook (called by isEmailConfirmed) will be called in an additional scenario. However, isEmailConfirmed seems to be called frequently already (e.g. by both canSendEmail and canReceiveEmail).

The fix means you can do something user-facing (e.g. sending an email to the user) on ConfirmEmailComplete without that occurring twice if the URL is visited again when they're already confirmed.