Current version doesn't seem to be associating different profiles by a common (if present) email address. In fact, the model UserEmail (which I believe is the responsible of this association) seems to never be created at all.
I would expect the UserEmail to be created in the following method of the User model:
@classmethod
def _get_or_create(cls, auth_id, emails, **kwarg):
assert isinstance(emails, list), 'Emails must be a list'
user = cls._find_user(auth_id, emails)
# if user and emails is not None:
# user._add_emails(emails)
if user is None:
user = cls._create_user(auth_id, **kwarg)
return user
But that part of the code is commented out, and I can't find the reason in the logs. Is it safe to remove the comments?, is the User<-Email->UserProfile association done here, or am I completely clueless?.
Thank you so much!
Current version doesn't seem to be associating different profiles by a common (if present) email address. In fact, the model UserEmail (which I believe is the responsible of this association) seems to never be created at all.
I would expect the UserEmail to be created in the following method of the User model:
But that part of the code is commented out, and I can't find the reason in the logs. Is it safe to remove the comments?, is the User<-Email->UserProfile association done here, or am I completely clueless?.
Thank you so much!