On Fri, Dec 30, 2005 at 05:13:52PM +, Afternoon wrote:
>
>
> Django developers: when people start using monkey patches to get
> around issues, it's time to prioritise fixing them properly.
>
> This has been discussed many times and several solutions proposed.
>
> Worse things could happe
Django developers: when people start using monkey patches to get
around issues, it's time to prioritise fixing them properly.
This has been discussed many times and several solutions proposed.
Worse things could happen that just using this as the template for a
patch.
On 28 Dec 2005,
I found this "hack" that does it very nicely. Forgot who gave me the
link; and the link itself :(
from django.models.auth import User
def user_pre_save(self):
if not self.password.startswith('sha1$'):
self.set_password(self.password)
User._pre_save = user_pre_save
Add this in your mode
> but in the user-management part, the password has to be entered in an
> md5-hashed form.
hi gabor,
I've been thinking about this as well and my solution is probably going
to be something like the following:
1) Create a custom form with only the username/password/confirm fields.
This will take
On 12/27/05, gabor <[EMAIL PROTECTED]> wrote:
> how do other django developers solve this problem?
> do they create a separate view to handle user management?
I've been lobbying forever to just have a _pre_save hook added which
hashes the password, and I'd imagine that'd be the most expedient way
for a website i'm working on, we need user management.
the standard django stuff works fine,
so our idea is/was to simply give some users access to the admin
interface, so they can use it to fill in the data, manage their own
users and so on.
but in the user-management part, the password has t
6 matches
Mail list logo
