On 8/3/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > The traditional approach is that they are password entry boxes that are > empty and you only pay attention in the form processing if they contain > something (in which case the two entries must match, etc). I would have > though that worked fairly well in our case as well?
I'm not a huge fan of that approach -- it's kind of "magic." I'm leaning toward the solution of hiding the password from the "Change user" page and creating a separate, special-case "Change password" view. This would be different from the user-facing "Change password" view, as it would be used by admins. I'm not too passionate about it either way, but I'm just glad we've finally fixed the "Add user" thing. Adrian -- Adrian Holovaty holovaty.com | djangoproject.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
