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

Migrate users to use the django built in active flag instead of the custom approved flag in UserProfile #614

Open
CarvellWakeman opened this issue Jan 3, 2018 · 2 comments

Comments

@CarvellWakeman
Copy link
Contributor

No description provided.

@hertelc
Copy link
Collaborator

hertelc commented Jan 4, 2018

@CarvellWakeman done?

@CarvellWakeman
Copy link
Contributor Author

Nope, I wanted to wait on this because it's technically not necessary, but should have been done from the get go. It might enable some security features for us because the django built in is_active flag some some stuff for you automatically. We are using a custom column for our userProfile object called approved.

There was probably some reason for the decision, but I have no idea what it was.

@hertelc hertelc added this to the Production 1.1.0 Release milestone Feb 19, 2018
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