Dear James,
Thanks for your reply.
1. I'll investigate using the "Django debug toolbar".
2. re: "extraneous classes": I was trying to make a point of how to
construct the second-2 classes from the first-2. The second-2 classes (CRUD
classes) are a *text copy* of the first-2 with the difference being that
the second-2 have their names changed, in the appropriate 2 places & (I
THOUGHT) they point to A DIFFERENT Crud Template ('contacts/crudlist.htm').
The Crud Template IS NOT USED FOR RENDERING. INSTEAD the Template mentioned
in the first-2 classes is used.
3. re: "template inheritance structure". Any Django Docs on this subject?
I'll investigate the Debug Toolbar & see what it tells me.
Again, THANKS, BIG TIME, James.
Love and peace,
Joe
On Saturday, June 18, 2016 at 10:52:46 PM UTC-7, James Schneider wrote:
>
> > I EXPECT the Views with CRUD in their names (CRUD Views) to behave THE
> SAME AS the others EXCEPT items are listed with read, update & delete
> links, because that is how `contacts/crudlist.htm` displays them.
> >
> > THE PROBLEM IS that the CRUD Views display the items using the Plain
> Template (contacts/contact_list.html) NOT the CRUD Template
> ('contacts/crudlist.htm')
> >
>
> The Django debug toolbar can likely illuminate the problem here, or at
> least provide a direction. You would need to verify the template(s) that
> have been rendered as part of your view call, and that they're actually
> doing what you think they're doing.
>
> It's a bit hard to follow your code, as you include extraneous classes
> that don't appear to be relevant to the problem (no inheritance, no
> indication they've been triggered, etc.). With that being said, your output
> from the view appears to be correct and shows a different (and correct)
> template_name for each view. I might be missing something though, and
> admittedly I'm responding on my phone.
>
> My assumption at this point would be that the templates are rendered
> correctly by Django (correctly meaning 'as configured'), and that the issue
> actually lies within your template inheritance structure (if any). Again,
> the debug toolbar will walk you through that.
>
> -James
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/34148840-2e69-4712-9094-f3a7baadb66e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
