From b1c2e80187008aff472c6509c67f44583cd3334c Mon Sep 17 00:00:00 2001 From: Stephen Finucane Date: Sat, 3 Nov 2018 21:47:51 +0000 Subject: models: Ensure UserProfile.user is configured Django Admin seems to be doing something funky with how it's handling the creation of a User's corresponding UserProfile instance when modelled as an inline field. Re-setting the UserProfile.user attribute seems to resolve the issue, so do just that. Signed-off-by: Stephen Finucane Closes: #110 --- patchwork/models.py | 1 + releasenotes/notes/issue-110-a5bb3184bf831280.yaml | 5 +++++ 2 files changed, 6 insertions(+) create mode 100644 releasenotes/notes/issue-110-a5bb3184bf831280.yaml diff --git a/patchwork/models.py b/patchwork/models.py index a483dc6..a7eee4d 100644 --- a/patchwork/models.py +++ b/patchwork/models.py @@ -194,6 +194,7 @@ class UserProfile(models.Model): def _user_saved_callback(sender, created, instance, **kwargs): try: profile = instance.profile + profile.user = instance except UserProfile.DoesNotExist: profile = UserProfile(user=instance) profile.save() diff --git a/releasenotes/notes/issue-110-a5bb3184bf831280.yaml b/releasenotes/notes/issue-110-a5bb3184bf831280.yaml new file mode 100644 index 0000000..16a0fa5 --- /dev/null +++ b/releasenotes/notes/issue-110-a5bb3184bf831280.yaml @@ -0,0 +1,5 @@ +--- +fixes: + - | + Assigning maintained projects when creating a new user in the admin page + was causing an error. This is now resolved. -- cgit v1.2.3