Thanks a lot. To make it clear, do I understand right that you have some custom view to process APIPasswordChangeForm and not using django.contrib.auth.views.password_change?
On Sunday, December 14, 2014 2:17:16 PM UTC+4, Josh Smeaton wrote: > > https://gist.github.com/jarshwah/c5b9abebb452f2e3286f > > I've removed some of the error handling and custom application bits, and > I've also renamed the classes. But this is the meat of auth for my project. > You'll notice that the backend is hardcoded in the constructor, because we > only use this backend. If you had multiple, you'd need to figure out which > backend or form to show, but that should be trivial. The built-in auth > already caches the backend in use, so you could just check that property I > think. > > Regards, > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/a7726193-fb52-40db-85f8-d3fad0cfa003%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
