Are you trying to create both the User and the Profile in the same view?
Yes, as they are intrinsically linked, and I don’t want the admin to have to create a user, and then create a profile.
I think with ControlProfileCreateView I tried it with both User and Profile as the model. Same result.
Sorry, what I meant about the AUTHENTICATION_BACKENDS was that this is what sets-up allauth to manage the auth_user, of course the relationship between User and ``Profile``` is as you write.
Hmm, so maybe a formset would be in order?
While I’m here, you will notice that this line, above, is commented out:
#id = models.CharField(primary_key=True, default=shortuuid.uuid, max_length=31)
I would like to use UUIDs for at least some of the primary keys, but when using this form every time I run makemigrations it reports tha the id field has changed – when I know that it has not. Has anyone else recommendations for UUID/randomised ID generation in django?
Thanks