I am creating a Django app for which I want to be able to approve users before letting them login to the site. Am using django-user-accounts from pinax for the same. This approval step requires users to submit additional information such as their qualifications etc. This information should be asked after the registration page and stored with their profile. Even after they have confirmed their email, they shouldn't be able to login unless admin has approved them.
I am confused between two options : 1) Over-ride registration flow and show the profile edit form (where the profile has been created by post_save signal). But the profile-edit view should have some kind of authentication too right? how do I ensure it takes only the value passed from registration page and nothing else? 2) Login user after registration and show him his profile edit page. This page is the shown until he's filled it in after which he sees the waiting for admin approval text. This will be achieved with a mixin which will then be inherited by all my views. My concern here is the database fetch which will occur each time this mixin is run. This seems like a pretty common flow. What's the best way to achieve this? Thanks -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/298fa580-1cc9-4164-95fe-3f743094ca7a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
