Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

activation_key must be unique #70

Closed
LennyLip opened this issue Jan 14, 2017 · 1 comment
Closed

activation_key must be unique #70

LennyLip opened this issue Jan 14, 2017 · 1 comment

Comments

@LennyLip
Copy link

RegistrationProfile.activation_key must be uniqie=True, because we use "get" by
https://github.com/ubernostrum/django-registration/blob/master/registration/models.py#L52

also ALREADY_ACTIVATED , i think, better change to activation datetime field.

@ubernostrum
Copy link
Owner

You seem to have closed this yourself, but: the model-based backend is only in django-registration now for backwards-compatibility purposes, and will likely be removed in 3.0. Since it exists only to provide backwards compatibility, it will never have backwards-incompatible changes made to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants