If we delete the `email_address` records (and I think we should), we'll have to make sure that if/when the user is activated again, the `email_address` records are re-created based on the `user.email_addresses` field.
--- ** [tickets:#7761] Disabling a user does not remove/disable his primary email** **Status:** open **Milestone:** forge-oct-17 **Created:** Sun Oct 12, 2014 04:31 PM UTC by Alexander Luberg **Last Updated:** Sun Oct 12, 2014 04:31 PM UTC **Owner:** nobody 1) Sign up a user with email [email protected] 2) Verify his account/email 3) From user prefs - disable this account 4) Sign up a new user with the same email [email protected] 5) Verify his account/email 6) Password recovery won't work for him(And most probably we will run into some other issues) email_address collection state: ~~~~~ > db.email_address.find({email: '[email protected]'}) { "_id" : ObjectId("5436e94d01a61326884419c6"), "nonce" : null, "claimed_by_user_id" : ObjectId("5436e94d01a61326884419a0"), "confirmed" : true, "email" : "[email protected]" } { "_id" : ObjectId("543aaa0601a61361523e52ac"), "nonce" : null, "claimed_by_user_id" : ObjectId("543aaa0601a61361523e5286"), "confirmed" : true, "email" : "[email protected]" } ~~~~~ first one is linked to the disabled user, the second one to the current, active user. --- Sent from sourceforge.net because [email protected] is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
