On May 30, 2006, at 9:58 AM, James Bennett wrote:
>
> On 5/30/06, stane <[EMAIL PROTECTED]> wrote:
>> to create password open python shell
>> import md5
>> md5.new('password').hexdigest()
>>
>> copy string into password field
>
> Or use the 'set_password' function defined in Django's auth module.
But my point was that, if you find yourself editing a user whose
password hasn't been set, setting the password is not optional. The
form won't pass validation without it. And the thing you have to type
in the password field is almost impossible to come up with without
extra help (such as a Python shell).
Just from a usability perspective, I don't think you should strand a
user in a form that won't validate unless they can enter something
that (if they're not a developer, just an admin user administering
the site) they'll have no idea how to enter.
Isn't the most probable use case where a developer will set up a site
and then expect a non-technical admin to create a bunch of accounts,
or at least to create accounts that come up after development is
finished? If that's the case, the inability to enter the password as
plain-text means this use case can't work.
Todd
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
