On 9/28/06, Enrico <[EMAIL PROTECTED]> wrote: > > Hi Waylan, > > Thanks for your help, the fog has gone now. :)
Just to further Waylan's comments: The purpose of 'is_active' is to identify an 'active' user - that is, a user whose account can still be used to log in. This is an alternative to deleting an account when you want to remove access for a user. If there are artefacts in your database that reference a specific user (e.g., a comment), you may not want to delete the user, as this would delete the related artefacts. > Maybe the docs should be a little clearer... Do you have any specific suggestions? Is there any specific area that you feel could be improved? Something that has been ommitted? Something that is misleading? The documentation on authentication describes is_active in the API reference for the fields of the User model - is this description inadequate? Should it be repeated/referenced somewhere else? Specific requests and/or specific problems can be addressed and fixed; blanket statements tend to get ignored due to a lack of telepathy on the part of the developers :-) Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
