Opened 17 years ago
Closed 17 years ago
#5948 closed (wontfix)
MyApp priority in template loader app_directories
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | Template system | Version: | dev |
Severity: | Keywords: | template loader priority | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Now, the template loader app_directories use the priority of applications order. I think that is more important the priority of the current application, for search templates with same name.
Other possibility is create a new template loader for load my app templates and the django user locate it before app_directories loader.
Note:
See TracTickets
for help on using tickets.
It's only accidental (and not to be relied upon) that even application listing order is used for the app_loader. If you have two templates with the same name (including parent directories below template/) and you're using the app_loader, anything can happen (so don't do that). It's not always going to be correct to give priority to the "current" application, since (a) there may not be a current application because views can come from anywhere and (b) it impedes sharing between applications.
So I think this isn't something we're going to change. We also don't really need yet another template loader in the standard list just for this case, I feel (although obviously you can write a third-party one if you need it).