Re: Problem with views PasswordChangeView vs. password_change

2017-07-14 Thread Carsten Fuchs
Am 13.07.2017 um 22:44 schrieb Tim Graham: The success_url of PasswordChangeView (actually the behavior comes from the inherited FormView) only accepts a URL, not a URL name. You can update to your code like this: from django.urls import reverse_lazy ... success_url=reverse_lazy('lori:pwd_done')

Re: Problem with views PasswordChangeView vs. password_change

2017-07-13 Thread Tim Graham
The success_url of PasswordChangeView (actually the behavior comes from the inherited FormView) only accepts a URL, not a URL name. You can update to your code like this: from django.urls import reverse_lazy ... success_url=reverse_lazy('lori:pwd_done') On Thursday, July 13, 2017 at 11:44:43 A

Re: Problem with views PasswordChangeView vs. password_change

2017-07-13 Thread Carsten Fuchs
Am 13.07.2017 um 16:56 schrieb Carsten Fuchs: the success_url='lori:pwd_done' seems to be a problem This seems to be the root also of the original problem (SuspiciousOperation…): If I insert a plain URL, e.g. success_url='/pwd_done/', then I can no longer reproduce the original problem ei

Re: Problem with views PasswordChangeView vs. password_change

2017-07-12 Thread Tim Graham
Hi, I can't reproduce that error. Can you provide a sample project? Maybe it has something to do with the ggVerfallenMiddleware? On Wednesday, July 12, 2017 at 10:48:25 AM UTC-4, Carsten Fuchs wrote: > > Dear Django group, > > using Django 1.11.3 with Python 2.7, please consider the following t

Problem with views PasswordChangeView vs. password_change

2017-07-12 Thread Carsten Fuchs
Dear Django group, using Django 1.11.3 with Python 2.7, please consider the following test: def test_passwort_aendern(self): u = User.objects.create_user("Test", "t...@example.com", "Passwort") self.client.force_login(u) response = self.client.post("/change_passwor