Homec4science

Recover more flexibly from an already-verified email

Authored by epriestley <git@epriestley.com> on Nov 21 2013, 23:41.

Description

Recover more flexibly from an already-verified email

Summary:
Ref T4140. We could hit a redirect loop for a user with a verified primary email address but no "is verified" flag on their account. This shouldn't be possible since the migration should have set the flag, but we can deal with it more gracefully when it does happen (maybe because users forgot to run storage/upgrade, or because of ghosts).

In the controller, check the same flag we check before forcing the user to the controller.

When verifying, allow the verification if either the email or user flag isn't set.

Test Plan: Hit /login/mustverify/; verified an address.

Reviewers: btrahan

Reviewed By: btrahan

CC: aran

Maniphest Tasks: T4140

Differential Revision: https://secure.phabricator.com/D7621

Details

Committed
epriestley <git@epriestley.com>Nov 21 2013, 23:41
Pushed
aubortJan 31 2017, 17:16
Parents
rPH13275860b18e: When stopping on redirect, show a full stack trace
Branches
Unknown
Tags
Unknown

Event Timeline

epriestley <git@epriestley.com> committed rPH3a035c02e7b9: Recover more flexibly from an already-verified email (authored by epriestley <git@epriestley.com>).Nov 21 2013, 23:41