#10245: All Authentication built in views assume that default templates and paths are used ----------------------------------+----------------------------------------- Reporter: sfgreenwood | Owner: nobody Status: new | Milestone: post-1.0 Component: Documentation | Version: 1.0 Keywords: auth, built-in views | Stage: Unreviewed Has_patch: 0 | ----------------------------------+----------------------------------------- The documentation for the built in views in the Authentication battery, such as django.contrib.auth.views.password_change() says that the only optional argument is template_name if not using the default. Using a different template_name causes a NoReverseMatch error. Looking at the code, there is a second argument, post_change_redirect, which has to be defined if a different path from the default is used. Other, similar arguments apply to password_reset() for post_reset_redirect and email_template_name. These additional arguments should be documented. I would suggest that ideally there should no defaults at all and the paths and templates should be defined in settings.py or in a separate configuration file.
-- Ticket URL: <http://code.djangoproject.com/ticket/10245> Django <http://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 post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-updates?hl=en -~----------~----~----~----~------~----~------~--~---
