Hi all,
I like the idea of a "Change password" view.
It doesn't feel like changing the password by mistake.
But wouldn't hurt to use the "not-empty" approach, what matters is to
have this feature.
Regards.
Enrico
--~--~-~--~~~---~--~~
You received this message
One word: Amen.
--~--~-~--~~~---~--~~
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
On Thu, 2006-08-03 at 23:42 -0500, Adrian Holovaty wrote:
> 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
On 04/08/2006, at 3:37 PM, Malcolm Tredinnick wrote:On Fri, 2006-08-04 at 15:13 +1000, Ian Holsman wrote:[...] I like the idea of a change password view, could I twist your arm a bit and make it a 'generate random passwordand email it to the user view' instead of 'set password' ?and possibly have
On Fri, 2006-08-04 at 15:13 +1000, Ian Holsman wrote:
[...]
> I like the idea of a change password view,
> could I twist your arm a bit and make it a 'generate random password
> and email it to the user view' instead of 'set password' ?
> and possibly have the email point the user to a view to
On 04/08/2006, at 2:42 PM, Adrian Holovaty wrote:On 8/3/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: The traditional approach is that they are password entry boxes that areempty and you only pay attention in the form processing if they containsomething (in which case the two entries must
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
On 04-Aug-06, at 9:54 AM, Adrian Holovaty wrote:
> In revision 3520, I checked in a fix to a longstanding problem (ticket
> #61) -- having to enter password hashes when creating users via the
> Django admin site. The "Add user" page now lets you put in the
> username and raw password, via two
On Thu, 2006-08-03 at 23:24 -0500, Adrian Holovaty wrote:
> In revision 3520, I checked in a fix to a longstanding problem (ticket
> #61) -- having to enter password hashes when creating users via the
> Django admin site. The "Add user" page now lets you put in the
> username and raw password,
In revision 3520, I checked in a fix to a longstanding problem (ticket
#61) -- having to enter password hashes when creating users via the
Django admin site. The "Add user" page now lets you put in the
username and raw password, via two HTML "input type=password" fields.
The code is also a
10 matches
Mail list logo
