#10864 closed (fixed)
Clarify that "next" is the default for redirect_to_field
| Reported by: | trigeek38 | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Keywords: | next, login_decorator | |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Section described: http://docs.djangoproject.com/en/dev/topics/auth/#the-login-required-decorator.
The use of the 'next' and 'redirect_to_field' is not clear. I think this section deserves a little more description of how to use the decorator correctly.
Current:
"If the user isn't logged in, redirect to settings.LOGIN_URL (/accounts/login/ by default), passing the current absolute URL in the query string as next or the value of redirect_field_name. For example: /accounts/login/?next=/polls/3/."
Addition:
"You can pass this value to the login form to complete the request after successful login. See views.login() below for an example.
Attachments (1)
Change History (5)
comment:1 by , 16 years ago
| milestone: | 1.1 |
|---|
comment:2 by , 15 years ago
| Has patch: | set |
|---|---|
| Summary: | Helpful addition for use of @login_required. → Clarify that "next" is the default for redirect_to_field |
| Triage Stage: | Unreviewed → Ready for checkin |
| Version: | 1.0 → SVN |
by , 15 years ago
| Attachment: | 10864.diff added |
|---|
comment:3 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:4 by , 15 years ago
Note:
See TracTickets
for help on using tickets.
(In [11544]) Fixed #10864 -- Clarified the role played by redirect_to_field in the login_required auth decorator. Thanks to trigeek38 for the suggestion, and SmileyChris for the draft.