Question: Using a custom `ACCOUNT_ADAPTER`

[mscheper]

I'm using Django Invitations and AllAuth, and I want to set defaults on the sign-up page, based on a previously created table containing verified email addresses. I've thus subclassed BaseInvitationsAdapter and overridden new_user.

But I want Invitations to keep working, particularly the INVITATIONS_ACCEPT_INVITE_AFTER_SIGNUP setting. So it seems I should subclass Django Invitations' InvitationsAdapter. But that's only possible to import when ACCOUNT_ADAPTER == "invitations.models.InvitationsAdapter", so if I change INVITATIONS_ACCEPT_INVITE_AFTER_SIGNUP to my own subclass, that function will stop working (and the code won't run, since the superclass disappears).

I'm basically having the same issue as #99, but the solution to that seems a hack to me—that adapter must surely be 'hidden' for a reason. The code says InvitationsAdapter only exists for historic reasons, so I must've missed the contemporary way of doing it. I can't find it in the docs, though.

Could you point me to how, please?

[mscheper]

It looks like #143 is a similar use case, and they talk about using signals there. I realise I can act on the user_signed_up signal, but is there a way to tell whether the user signed up via an invitation, and thus that the email is verified?

[mscheper]

@clokep: It seems you wrote the comment that says InvitationsAdapter only exists for historic reasons. I know I'm asking about something you wrote 10 years ago, but can you shed light on the intended way of doing this? Thanks.

[clokep]

I'm basically having the same issue as #99, but the solution to that seems a hack to me—that adapter must surely be 'hidden' for a reason. The code says InvitationsAdapter only exists for historic reasons, so I must've missed the contemporary way of doing it. I can't find it in the docs, though.

I think the reason is that the automatic allauth integration is "deprecated" and if you wish to integrate with allauth you're expected to do it yourself. This was to make django-invitations agnostic to the authentication provider.

I think the contemporary way is what's in #99? I'm not sure which part of it is hack-y.

It has been a very long time since I've looked at anything to do with this package though so I might not be remembering correctly.

But I want Invitations to keep working, particularly the INVITATIONS_ACCEPT_INVITE_AFTER_SIGNUP setting

This looks like it is mostly handled in the view, not the adapter. But maybe that doesn't help you.