On Wed, 2008-02-06 at 11:31 -0800, Daniel Roseman wrote:
> >From the same documentation page you quote above (http://
> www.djangoproject.com/documentation/templates/):
>
> When you load a custom tag or filter library, the tags/filters are
> only made available to the current template -- not any parent or child
> templates along the template-inheritance path.
> For example, if a template foo.html has {% load comments %}, a child
> template (e.g., one that has {% extends "foo.html" %}) will not have
> access to the comments template tags and filters. The child template
> is responsible for its own {% load comments %}.
> This is a feature for the sake of maintainability and sanity.
Thanks for the info. At least I know I'm not missing something. It
does seem to interfere with DRY since I have to repeat {% load %} (in my
case, there are 2) in each child template.
> RE the extends tag placement, this is a recent change in the trunk
> (there's a thread talking about it in django-developers now). You're
> looking at the SVN documentation but using 0.96 - you might be better
> off following the link at the top of the page to the 0.96
> documentation.
I took the quote from the v0.96 doc
(http://www.djangoproject.com/documentation/0.96/templates/).
--
Adam Stein @ Xerox Corporation Email: [EMAIL PROTECTED]
Disclaimer: All views expressed
here have been proved to be my own. [http://www.csh.rit.edu/~adam/]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
