On Mon, 2008-12-15 at 10:01 -0800, Jeff Kowalczyk wrote: > On Dec 13, 9:31 pm, Malcolm Tredinnick <malc...@pointy-stick.com> > wrote: > > That sounds like the only way. If you want to see batchadmin's changes, > > you have to extend from that. > > Thank you, I have made batchadmin find its media in my development > setup. > > My change_list.html, which now extends batchadmin/change_list.html, is > not > selected for rendering/has no effect in the filesystem layout I would > expect to > work, and recursion error problems in next most likely layout. > > The following layout results in a recursion error:
Seriously. :-( The remainder of your message is almost 400 lines long. That's in addition to me having to know about batchadmin, which I have no knowledge of. I'm all for helping out on mailing lists, but there is a limit to the charity! So let's fall back to first principles: always construct the smallest case possible that repeats the failure. This means start with a template that includes nothing but the "extends" of the batchadmin template. If that works, you can start adding in the other lines until things stop working and then back up a step to work out the problem that arises. If the single line template does not work, you have a one-line template that you can start debugging. It is *much* simpler. Good luck, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
