See http://code.djangoproject.com/ticket/61 for discussion and
http://code.djangoproject.com/wiki/CookBookPasswordGreasemonkeyUserScript
for a client-side solution while waiting for Django to be fixed.
--~--~-~--~~~---~--~~
You received this message because you ar
On Sun, 23 Apr 2006 15:11:46 -0500, Adrian Holovaty wrote:
> This is on the to-do list. We're focusing on the magic-removal merge
> first, though; feature additions have been frozen for the moment.
Of course, I understand the concept of feature freeze :-)
I need this for work, so I'll code it to
On 4/23/06, Lalo Martins <[EMAIL PROTECTED]> wrote:
> To the Django composers: can we pleeease have a real password field?
> And use that for User rather than all that contortion? It's of very
> limited usefulness to see the raw password in the admin, and it makes it
> impossible for a non-geek t
Ok, create_user is now User.object.create_user for those wondering.
To the Django composers: can we pleeease have a real password field?
And use that for User rather than all that contortion? It's of very
limited usefulness to see the raw password in the admin, and it makes it
impossible for a
4 matches
Mail list logo
