Opened 3 years ago

Last modified 3 years ago

#33632 closed Bug

Overwriting 'context_object_name' in list views — at Initial Version

Reported by: Iván Legrán Owned by: nobody
Component: Generic views Version: 4.0
Severity: Normal Keywords: generic views context_object_name
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

I have found that when I override the context object name in a ListView it is impossible for me to iterate correctly in a for loop in the template. For example, if I am writing a list view called 'Services' and override the context object name as 'services', using the for loop as follows:

{% for service in services %}

<p>

{{ service.name }}

</p>
<p>

{{ service.description }}

</p>

{% endfor %}

I find that instead of iterating over the number of items that I have stored in the database, it does so over a crazy number of items that I don't know what they are related to.

The same code works perfectly on Django 3.xx, and I can iterate normally in the loop if I use the 'object_list' which its provided by default.

Change History (0)

Note: See TracTickets for help on using tickets.
Back to Top