Extra field in custom registration in DRF won't save

Question

I created a custom serializer that extends dj_rest_auth's RegisterSerializer, added the extra user_type field, overrode the get_cleaned_data method to include the user_type in the cleaned data then configured the custom registration serializer used for registration.

Here's my code:

class CustomRegisterSerializer(RegisterSerializer):

    user_type = serializers.ChoiceField(choices=[('seeker', 'Seeker'), ('recruiter', 'Recruiter')])

    class Meta:
        model = User
        fields = "__all__"

    def get_cleaned_data(self):
        data = super().get_cleaned_data()
        data['user_type'] = self.validated_data.get('user_type', '')
        return data

class Profile(models.Model):
    class Type(models.TextChoices):
        seeker = "Seeker"
        recruiter = "Recruiter"
    
    base_type = Type.seeker
    user = models.OneToOneField(User, on_delete=models.CASCADE)
    user_type = models.CharField(choices=Type.choices, default=base_type, max_length=20)

    class Meta:
        verbose_name = "Profile"
        verbose_name_plural = "Profiles"

    def __str__(self):
        return self.user.username

class CustomRegisterView(RegisterView):
    serializer_class = CustomRegisterSerializer

And? What is happening? You don't give any details of the actual problem here. — michjnich, Aug 15 '23 at 07:16
And you gave zero info about what was actually happening, any trace info etc. — michjnich, Aug 15 '23 at 11:58

score 1 · Accepted Answer · answered Aug 15 '23 at 07:57

1

There's a piece missing in your code. You've added the user_type to the cleaned data but haven't shown how the Profile gets created and how the user_type is stored in the Profile model when a new user registers.

Here's how you can complete the registration process by creating the associated profile:

Override the save method in your CustomRegisterSerializer.

class CustomRegisterSerializer(RegisterSerializer):

    # ... [rest of your code]

    def save(self, request):
        user = super().save(request)
        user_type = self.validated_data.get('user_type')
        Profile.objects.create(user=user, user_type=user_type)
        return user

answered Aug 15 '23 at 07:57

Mihail Andreev

979
4
6

This made the `user_type` field disappear from the registration fields. weird – Vicente Antonio G. Reyes Aug 15 '23 at 08:39
1

When you override the save method of the serializer, it shouldn't affect the displayed fields in any way. The fields that are displayed are based on the serializer fields you define and shouldn't be affected by the logic within the save method. – Mihail Andreev Aug 15 '23 at 08:47
Disregard the comment. I went to the wrong `url`. Now I'm getting a `django.db.utils.IntegrityError: UNIQUE constraint failed: accounts_profile.user_type` you know what's causing this? – Vicente Antonio G. Reyes Aug 15 '23 at 08:53
https://stackoverflow.com/questions/76904746/django-db-utils-integrityerror-unique-constraint-failed-accounts-profile-user – Vicente Antonio G. Reyes Aug 15 '23 at 09:24
1

Do you have the error when you create a new one or update the existed one? – Mihail Andreev Aug 15 '23 at 11:06
This is solved thanks – Vicente Antonio G. Reyes Aug 15 '23 at 11:09
1

Always happy to help. <3 Please thumbs up if the answer is useful. – Mihail Andreev Aug 15 '23 at 11:19
Can you help me with this aswell? The problem is the link that django-allauth is sending should be the one I created https://stackoverflow.com/questions/76905060/dj-rest-auth-templateresponsemixin-requires-either-a-definition-of-template-nam/76905128#76905128 – Vicente Antonio G. Reyes Aug 15 '23 at 11:21

Extra field in custom registration in DRF won't save

1 Answers1