Malcolm Tredinnick <malc...@pointy-stick.com> wrote:
> 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.
I did put some time into recreating the interaction problem with two
generic startapps. It didn't go so well until I understood the
problem.
I found that setting change_list_template on my derived class allowed
me to select the template from it's original location prior to adding
batchadmin.
widgets/admin.py:
class WidgetAdmin(BatchModelAdmin):
change_list_template = "admin/widgets/widget/change_list.html"
batchadmin/admin.py:
class BatchModelAdmin(admin.ModelAdmin):
change_list_template = "batchadmin/change_list.html"
> The remainder of your message is almost 400 lines long.
I have to claim list word-wrapping there. My carefully-prepared
description of an interaction between reusable apps was a svelte 349
lines as composed ;) Seriously though, I plan to omit the template
listings next time.
Thanks,
Jeff
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
