Bug #6851
error when trying to change password
100%
Description
When trying to change the password change page(accounts/password/reset/
), the following error occurs
Reverse for 'password_reset_done' with arguments '()' and keyword arguments '{}' not found. 0 pattern(s) tried: []
Fichiers
Révisions associées
accounts: use Django naming for password related views, keep previous name for retrocompatibility with already deployed themes (#6851)
Django 1.7 now use accounting view names directly in its code, they also
changed the signature of the password_change_done view regexp (it
expects a uidb64 argument instead of uidb36). To minimize difference
with expected view names but to also keep retrocompatibility view names
were renamed with the Django names and old declarations were kept but
declared after the official ones such that they will never match a
request but they can still be used for reversing view names.
Historique
Mis à jour par Benjamin Dauvergne il y a environ 9 ans
- Fichier 0001-accounts-use-Django-naming-for-password-related-view.patch 0001-accounts-use-Django-naming-for-password-related-view.patch ajouté
- Assigné à changé de Serghei Mihai à Benjamin Dauvergne
- Patch proposed changé de Non à Oui
Django 1.7 now use accounting view names directly in its code, they also changed the signature of the password_change_done view regexp (it expects a uidb64 argument instead of uidb36). To fix this but to also keep retrocompatibility I changed our names for the Django names but I keps view declarations with the old names (and the old signature with uidb36).
Mis à jour par Benjamin Dauvergne il y a environ 9 ans
- Statut changé de Nouveau à Solution déployée
Mis à jour par Benjamin Dauvergne il y a environ 9 ans
- Statut changé de Solution déployée à Résolu (à déployer)
Mis à jour par Benjamin Dauvergne il y a presque 9 ans
- Statut changé de Résolu (à déployer) à Fermé
accounts: use Django naming for password related views, keep previous name for retrocompatibility with already deployed themes (#6851)
Django 1.7 now use accounting view names directly in its code, they also
changed the signature of the password_change_done view regexp (it
expects a uidb64 argument instead of uidb36). To minimize difference
with expected view names but to also keep retrocompatibility view names
were renamed with the Django names and old declarations were kept but
declared after the official ones such that they will never match a
request but they can still be used for reversing view names.