archive_index should have template_object_name

[marchino <marco.giusti@…>]

generic views archive_index and object_list are logically the same thing: a list of objects so they can use the same template but archive_index uses latest as template_object_name and object_list appends '_list' to it, so it is impossible to do this.

with this small patch is possible to use the same object name with both generic views. maybe you sould look deeper for a more consistency in generic views, i didn't.

[Thomas Kerpe]

Improved Patch against [6147] - added Documentation.

[Thomas Kerpe]

archive_index and object_list are not completly interchangable of course.
Also there is the issue with appending _list to template_object_name.
archive_index is somewhat inconsistent with that.

method	has template_object_name?	appends _list?
archive_index	no 1)	no
archive_year	yes	yes
archive_month	yes	yes
archive_week	yes	yes
archive_day	yes	yes
object_list	yes	yes

1) Patch will fix this

How to address the appending of _list without breaking something?
Adding it only if template_object_name was set is not consistent.

[Russell Keith-Magee]

(In [6157]) Fixed #3895 -- Added ability to customize the context variable in the archive_index generic view. Thanks to marco.giusti@… and toke-django@….

[chrisrobison]

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.

[Alex Gaynor]

This bug was fixed 2 years ago, if you think there is a new bug please file a new ticket.