Closed RomainFayolle closed 1 year ago
I was able to get another project using the same requirements. In fine, you have to merge your settings into a single var
REST_AUTH = {
'USER_DETAILS_SERIALIZER':
'cloud_api.apps.user.serializers.UserSerializer',
'OLD_PASSWORD_FIELD_ENABLED': True,
'PASSWORD_RESET_SERIALIZER':
'cloud_api.apps.user.serializers.CustomPasswordResetSerializer',
'REGISTER_SERIALIZER':
'cloud_api.apps.user.serializers.CustomRegisterSerializer',
'SESSION_LOGIN': False,
}
Hi !
I'm upgrading a project from Django 3.2.9 to 4.2.5, in a docker container. Previous project
requirements.txt
:I upgraded to
I switched to
dj-rest-auth
as asked indjango-rest-auth
https://github.com/Omaraitbenhaddi/django-rest-auth I only changed the imports and the name usage of the packages and run amigrate
command.Expected behavior: Project keep using
CustomRegisterSerializer
as before Actual behavior: Now, project ignoreCustomRegisterSerializer
and uses regularRegisterSerializer
instead. All resources online point to thesettings,py
but I have the correctREST_AUTH_REGISTER_SERIALIZERS
(I even tried to put my serializer inREST_AUTH_SERIALIZERS
instead). I also uninstalled and reinstalledallauth
. But keep getting the same issue:Because wrong Serializer is used. Any idea of what I did wrong in the migration ?
serializers.py
adapaters.py
urls.py
settings.py