#14778 closed (wontfix)
{load} for all child templates
Reported by: | Martin Tsachev | Owned by: | nobody |
---|---|---|---|
Component: | Template system | Version: | 1.2 |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
It would be nice if {load} worked for all child templates that used {extend} for the parent.
Change History (3)
comment:1 by , 14 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:2 by , 14 years ago
But this renders the custom filters/tags completely useless. It might make more sense to add custom filters as middleware in this case.
comment:3 by , 14 years ago
It's difficult to see how this renders custom filters/tags "useless".
It makes very good sense that a 'load' command should affect only the current template. If for example, a parent template deliberately loads a new filter/tag to override a builtin (like with the {% load url from future %}
which is recommended for Django 1.3), then it would be a bad thing if this propagated down to child templates which may not have been updated for this change.
This is for your own sanity. Please see: http://docs.djangoproject.com/en/dev/topics/templates/#custom-libraries-and-template-inheritance