On Jun 23, 11:03 pm, Karen Tracey <kmtra...@gmail.com> wrote:
> On Tue, Jun 23, 2009 at 10:22 PM, buttman <cp368...@ohio.edu> wrote:
>
> You seem to have left out of your options the choice of putting the {% with
> %} block in the parent template? Or passing your variables in the context
> with the names you'd like to use in the template blocks?
>
> Karen
I have a "base_form.html" template that is used for many different
kinds of forms. Sometimes "form.instance" is a "Position" object,
sometimes it's a "Company" object, etc. Each child template needs to
access "form.instance", but each child template doesn't use that
"form.instance" the same way. I can't use a context variable either
because a lot of these templates are being called from the
"create_update.update_object" generic view, where I'm kind of limited
to which extra variables I can give to the template. This is why I'm
kind of forced to use "form.instance" in the first place. I could
write wrapper functions for these generic views, but there are a ton
of them and it would take a long time :/
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
