On 9/10/06, Tamara D. Snyder <[EMAIL PROTECTED]> wrote: > I'd like to reuse the application next semester, with a different set > of students. And I naturally don't want my students to have any > access at all to the admin site.
The included backend should be sufficient for what you've described. Users can't log in to the admin unless they have the 'is_staff' flag set, so that's not a problem. And "expiring" the accounts of past students is easy enough by toggling their "is_active" bit (which makes for an easy lambda to pass into 'user_passes_test'). You could even periodically do cleanup by just deleting everyone whose account is inactive. -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
