Figured it out. I had a model form that included is_active as a field, but that field was not being displayed in the form for regular users. It was evidently unsetting the value.
On Mar 7, 5:08 pm, Malcolm Tredinnick <malc...@pointy-stick.com> wrote: > On Sat, 2009-03-07 at 10:12 -0800, jeff wrote: > > I'm finding random instances in my application where a new user > > registers or an existing user changes their password and then can't > > log in the next time because their account is no longer active. It > > doesn't happen consistently, which is driving me crazy. I am not > > using the authentication views that come with Django, but I am using > > the standard user class functions. > > > Is there something subtle about users and authentication that not > > aware of that might explain this? I'm explicitly setting a new user > > to active when they are created: > > No. There is nothing like that going on. You can grep through the source > to find all the instances where is_active is set or accessed if you > really want to be convinced. > > Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
