Hmmm, if you really want to send the password as you described it and have considered the arguments of my previous posters, why don't you make a pre-save method for your user model, which stores the clear text password in a simple extra model (just one-to-one with clear text pass and link to user profile). When the user activates, fetch the password from there, send it and then destroy the object.
Just my five cents though. Any opinions wether this is a bad idea? Jesore patrickk wrote: >thanks james, jay ... > >I do see your arguments. it´s just a litte bit frustrating ... >building the website using django was damn fast. now i´m stuck with >the registration process ... it already took me twice as long as >building the actual website. it´d be cool to have some kind of "best >practice" here. > >thanks, >patrick > >Am 18.07.2006 um 22:56 schrieb Jay: > > > >>Most systems do, if they don't send the password, they send a time >>sensitive link (randomly generated and hard to guess) that will >>take the >>user to a password change form where s/he gets to enter a new one. >> >>James Bennett wrote: >> >> >>>(but please note that's just me personally; the PasswordResetForm >>>manipulator actually will send the new password via email) >>> >>> >>> >>> >>> >> >> > > >> > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
