NoReverseMatch at /registration/password/change/

[NoviceSortOf]

...When attempting to use our template/registration/password_change_form.html

While Login, request password, logout and related functions are working without a problem.

When using password change we get the following error
"NoReverseMatch at /registration/password/change/"
 [SEE.: Full traceback below]

We are using Django 1.6

* Can anyone provide any insight as to why this might be occurring, solutions, or troubleshooting tips.

Thanks

Traceback information follows.
***************************************************
Request Method: GET
Request URL: https://rareorientalbooks.com/registration/password/change/

Django Version: 1.6.11.6
Python Version: 2.7.5
Installed Applications:
('django.contrib.auth',
 'django.contrib.contenttypes',
 'django.contrib.sessions',
 'django.contrib.sites',
 'django.contrib.admin',
 'django.contrib.humanize',
 'django.contrib.redirects',
 'bookstor',
 'bookstor.registration',
 'bookstor.profiles',
 'django_extensions',
 'django.contrib.admin',
 'bookstor.cart',
 'bookstor.books',
 'djangosecure')
Installed Middleware:
('django.middleware.common.CommonMiddleware',
 'django.contrib.sessions.middleware.SessionMiddleware',
 'django.middleware.common.CommonMiddleware',
 'django.contrib.auth.middleware.AuthenticationMiddleware',
 'django.middleware.transaction.TransactionMiddleware',
 'django.contrib.messages.middleware.MessageMiddleware',
 'django.contrib.redirects.middleware.RedirectFallbackMiddleware',
 'djangosecure.middleware.SecurityMiddleware')


Traceback:
File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py" in get_response
  112.                     response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/usr/lib/python2.7/site-packages/django/views/decorators/debug.py" in sensitive_post_parameters_wrapper
  75.             return view(request, *args, **kwargs)
File "/usr/lib/python2.7/site-packages/django/utils/decorators.py" in _wrapped_view
  99.                     response = view_func(request, *args, **kwargs)
File "/usr/lib/python2.7/site-packages/django/contrib/auth/decorators.py" in _wrapped_view
  22.                 return view_func(request, *args, **kwargs)
File "/usr/lib/python2.7/site-packages/django/contrib/auth/views.py" in password_change
  257.         post_change_redirect = reverse('password_change_done')
File "/usr/lib/python2.7/site-packages/django/core/urlresolvers.py" in reverse
  536.     return iri_to_uri(resolver._reverse_with_prefix(view, prefix, *args, **kwargs))
File "/usr/lib/python2.7/site-packages/django/core/urlresolvers.py" in _reverse_with_prefix
  456.                              (lookup_view_s, args, kwargs, len(patterns), patterns))

Exception Type: NoReverseMatch at /registration/password/change/
Exception Value: Reverse for 'password_change_done' with arguments '()' and keyword arguments '{}' not found. 0 pattern(s) tried: []

[m712]

Did you add all auth URLs to your URLconf? Also, please upgrade to at least Django 1.8 or (preferably) 1.11 they receive support for security issues while Django 1.6 does not.

--- :^) --- :^) --- :^) --- :^) --- :^) --- :^) --- :^) --- :^) ---
https://nextchan.org - https://gitgud.io/m712/blazechan
I am awake between 7AM-12AM UTC, hit me up if something's wrong

[NoviceSortOf]

Thanks for your reply.

>>> Did you add all auth URLs to your URLconf?

Thanks, we resolved the problems, by updating auth URLs as you mentioned and then also
modifying the related registration html pages, and custom registration views.

>> Also, please upgrade to at least Django 1.8 or (preferably) 1.11 they receive support for

>> security issues while Django 1.6 does not.

We appreciate the value of security updates, for now we must depend the variety of up to date mechanisms and services to block hacking and attacks provided by our web provider.

We have found upgrading between versions of Django not trivial.

We would hope that the upgrade from 1.6 to 1.8 would go smoother, at the moment though
we don't have the budget/resources to block  time for the task, even at the lower amount 

of estimated hours likely to be required.

Perhaps another thread, It would be interesting to know how many work hours other Django users spend with updates, and Linux distro migrations, I would suspect there would be a wide spectrum of cases, with more 

complex systems that include legacy customizations (such as ours) having a similar experience
with version upgrades being a non-trivial task.

Thanks