#9980 closed (invalid)
Nice-have correction for Authentication
| Reported by: | Sergiy Kuzmenko | Owned by: | Kevin Kubasik |
|---|---|---|---|
| Component: | Documentation | Version: | 1.0 |
| Severity: | Keywords: | templates authentication kkmegapatch | |
| 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
In http://docs.djangoproject.com/en/dev/topics/auth/#id5 the wording is a bit misleading. It would be nice to replace this:
The currently logged-in user, either a User instance or an AnonymousUser instance, is stored in the template variable {{ user }}
with this:
If rendering template django.template.RequestContext (link), the currently logged-in user, either a User instance or an AnonymousUser instance, is stored in the template variable {{ user }}
to make clear that this feature is only available with RequestContext (and not with Context)
Attachments (1)
Change History (7)
comment:1 by , 16 years ago
| Component: | Uncategorized → Documentation |
|---|
comment:2 by , 16 years ago
| milestone: | → 1.1 |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
by , 16 years ago
| Attachment: | requestcontext_auth_user.diff added |
|---|
comment:3 by , 16 years ago
| Has patch: | set |
|---|---|
| Triage Stage: | Accepted → Ready for checkin |
comment:4 by , 16 years ago
| Keywords: | kkmegapatch added |
|---|---|
| Owner: | changed from to |
comment:5 by , 16 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
In the paragraph directly above, it is already mentioned that you must be using RequestContext and that you need the correct context processor installed.
Note:
See TracTickets
for help on using tickets.
"Nice correction", slightly modified, in patch format