Opened 15 years ago
Closed 15 years ago
#10067 closed (invalid)
Modules for custom filters should be configurable
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Template system | Version: | 1.0 |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
When a filter module gets loaded by {% load foobar %}, django searches only in django/templatetags for the given module. Tha attached patch adds a configuration variable for modules where also to search for the filter module.
The attached patch can be applied with patch -p0
Attachments (1)
Change History (2)
by , 15 years ago
| Attachment: | tagload.diff added |
|---|
comment:1 by , 15 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
This seems to be based on a misunderstanding. The error message reported when there's a problem is a little misleading and we're intending to fix that (that's the subject of #6587). However, Django does not look in the directory you've indicated. It looks in the templatetags/ in each application registered via the INSTALLED_APPS setting. That's enough flexibility for our purposes (since you could create an application that only contains custom template tags, for example).
Patch to add a module search path