#32349: unable to obtain auth template password_reset_done when using namespaced
urls
----------------------------------+---------------------------------------
     Reporter:  millerthegorilla  |                    Owner:  jhabarsingh
         Type:  Bug               |                   Status:  assigned
    Component:  Template system   |                  Version:  3.1
     Severity:  Normal            |               Resolution:
     Keywords:  password_reset    |             Triage Stage:  Unreviewed
    Has patch:  0                 |      Needs documentation:  0
  Needs tests:  0                 |  Patch needs improvement:  0
Easy pickings:  0                 |                    UI/UX:  0
----------------------------------+---------------------------------------

Comment (by millerthegorilla):

 Now when I confirm the password change by clicking the email, I get a
 password confirm view, where I enter my two new passwords, and for some
 peculiar reason, honestly, when I click confirm, I get informed that there
 is no reverse match for the

 "Reverse for 'password_reset_complete' not found.
 'password_reset_complete' is not a valid view function or pattern name.

 I guess I would have to subclass PasswordResetConfirmView  but I am
 getting concerned that this is going to expose the possibility of hacking
 that view, since it no longer originates from contrib.auth.views.

 I also tried the following in my urls.py

 {{{
     path('password-reset-complete/',
          auth_views.PasswordResetCompleteView.as_view(
              template_name='users/password_reset_complete.html'
          ),
          name='password_reset_complete'),

 }}}
 and
 {{{
         path('password-reset-confirm/',
          auth_views.PasswordResetConfirmView.as_view(
              success_url='registration/password_reset_complete.html'
          ),
          name='password_reset_complete'),
 }}}

 This issue is so ****frustrating**** and has made the Django experience
 change from one that was really easy and useful, to one that is not only
 frustrating and wasting time, but one that looks possibly insecure as
 well.

 A comment that there is some possible good outcome to this ticket would be
 appreciated.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/32349#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/074.ffa9e9b275f52aede139d17cd0581123%40djangoproject.com.

Reply via email to