Yeah, this has been a big let down. What I'd hoped would be a few minutes setting up a basic site framework has turned into several hours wasted on boilerplate. The lack of docs, templates, and strange bugs like these leads me to think that django-registration isn't fully baked. I'm simply writing my own at this point, since I can't find a single example through Google of someone who's used that portion of registration successfully.
Chris On Wed, Oct 8, 2008 at 11:26 PM, meppum <[EMAIL PROTECTED]> wrote: > > That's odd, I was just about to post about a similar issue I was > having. Mine attempts to redirect but gives an error on the line > calling reverse to the password_change_done view. > > On Oct 8, 10:29 pm, Chris <[EMAIL PROTECTED]> wrote: >> Does anyone know of an example for using >> django.contrib.auth.views.password_change? >> >> All the docs seem to mention is how to specify it's template. After >> poking around in the code, I found it exposes new_password1 and >> new_password2 and I setup a basic form. However, it never redirects to >> the default password_change_done view, even though the passwords >> entered are identical. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
