{"action":"created","issue":{"url":"https://api.github.com/repos/macropin/django-registration/issues/93","labels_url":"https://api.github.com/repos/macropin/django-registration/issues/93/labels{/name}","comments_url":"https://api.github.com/repos/macropin/django-registration/issues/93/comments","events_url":"https://api.github.com/repos/macropin/django-registration/issues/93/events","html_url":"https://github.com/macropin/django-registration/issues/93","id":103487281,"number":93,"title":"Question: Would changing an email fit in this project?","user":{"login":"stringsonfire","id":3207366,"avatar_url":"https://avatars.githubusercontent.com/u/3207366?v=3","gravatar_id":"","url":"https://api.github.com/users/stringsonfire","html_url":"https://github.com/stringsonfire","followers_url":"https://api.github.com/users/stringsonfire/followers","following_url":"https://api.github.com/users/stringsonfire/following{/other_user}","gists_url":"https://api.github.com/users/stringsonfire/gists{/gist_id}","starred_url":"https://api.github.com/users/stringsonfire/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stringsonfire/subscriptions","organizations_url":"https://api.github.com/users/stringsonfire/orgs","repos_url":"https://api.github.com/users/stringsonfire/repos","events_url":"https://api.github.com/users/stringsonfire/events{/privacy}","received_events_url":"https://api.github.com/users/stringsonfire/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-08-27T11:21:22Z","updated_at":"2015-09-14T21:01:06Z","closed_at":null,"body":"Given a new email also needs to be activated, and the mechanism is in place here, is that something to think about including in django-registration-redux, or is it beyond the scope of this project?"},"comment":{"url":"https://api.github.com/repos/macropin/django-registration/issues/comments/140204783","html_url":"https://github.com/macropin/django-registration/issues/93#issuecomment-140204783","issue_url":"https://api.github.com/repos/macropin/django-registration/issues/93","id":140204783,"user":{"login":"dicato","id":542728,"avatar_url":"https://avatars.githubusercontent.com/u/542728?v=3","gravatar_id":"","url":"https://api.github.com/users/dicato","html_url":"https://github.com/dicato","followers_url":"https://api.github.com/users/dicato/followers","following_url":"https://api.github.com/users/dicato/following{/other_user}","gists_url":"https://api.github.com/users/dicato/gists{/gist_id}","starred_url":"https://api.github.com/users/dicato/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dicato/subscriptions","organizations_url":"https://api.github.com/users/dicato/orgs","repos_url":"https://api.github.com/users/dicato/repos","events_url":"https://api.github.com/users/dicato/events{/privacy}","received_events_url":"https://api.github.com/users/dicato/received_events","type":"User","site_admin":false},"created_at":"2015-09-14T21:01:05Z","updated_at":"2015-09-14T21:01:05Z","body":"After some debate, here is my plan for this:\r\n\r\n* connect a `pre_save` signal to the `User` model\r\n* in said signal compare the email address on the instance with the email address in the database using said instance's ID for lookup\r\n* if said emails differ, set `RegistrationProfile.activated` to `False` and kickoff the activation process\r\n\r\nThere are a bunch of challenges with re-starting the activation process (key reuse, etc) that I need to think though, but I believe the rough plan above should work.\r\n\r\nI think, at this point, this is something that should be on by default and not developer configurable."}}