Opened 11 years ago

Closed 11 years ago

#10067 closed (invalid)

Modules for custom filters should be configurable

Reported by: Ruediger Ranft <_rdi_@…> 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


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)

tagload.diff (1.5 KB) - added by Ruediger Ranft <_rdi_@…> 11 years ago.
Patch to add a module search path

Download all attachments as: .zip

Change History (2)

Changed 11 years ago by Ruediger Ranft <_rdi_@…>

Attachment: tagload.diff added

Patch to add a module search path

comment:1 Changed 11 years ago by Malcolm Tredinnick

Resolution: invalid
Status: newclosed

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).

Note: See TracTickets for help on using tickets.
Back to Top