Code

Opened 8 years ago

Closed 6 years ago

#1789 closed defect (fixed)

problem exists with list_detail.object_list generic view and subclassed models

Reported by: charlie.sheppard@… Owned by: nobody
Component: Generic views Version:
Severity: normal Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

A TemplateDoesNotExist exception occurs when using the object_list generic view with a Model that does not derive directly from models.Model. This is because it looks for <base model name>_list.html instead of <derived model name>_list.html.

Attachments (0)

Change History (4)

comment:1 Changed 7 years ago by Gary Wilson <gary.wilson@…>

  • Triage Stage changed from Unreviewed to Design decision needed

model subclassing in not yet supported.

comment:2 Changed 7 years ago by mtredinnick

  • Owner changed from jacob to mtredinnick

I'm pretty sure this gets fixed for free with model inheritance. On a technical level, the problem at the moment is just that the wrong model manager is installed for the subclass. That is one of the things that is fixed by the model inheritance changes.

Let's leave this open for now and revisit when I check those changes in. I'm pretty sure we'll find out it goes away at that point.

comment:3 Changed 7 years ago by mtredinnick

  • Triage Stage changed from Design decision needed to Accepted

comment:4 Changed 6 years ago by mattmcc

  • Resolution set to fixed
  • Status changed from new to closed

Indeed it did.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.