Opened 15 years ago
Closed 15 years ago
#11536 closed (invalid)
template_object_name not working correctly in archive_index
| Reported by: | chrisrobison | Owned by: | nobody |
|---|---|---|---|
| Component: | Generic views | Version: | |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Using template_object_name in archive_index is said to be fixed, however, I don't believe it is working how it should. I have created a date_based blog and once I assign a template_object_name of 'entry', I then have to change the template to something that seems backwards.
instead of:
{% for entry in latest %}
{% entry.title %}
it must be:
{% for latest in entry %}
{% latest.title %}
This is not consistent with the other date_based templates.
Change History (2)
comment:1 by , 15 years ago
comment:2 by , 15 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
I don't think it's a Django bug. It works as documented.
Please ask on django-users and reopen if you are sure that this is a Django bug.