tickets: 9093
This data as json
| id | created | changetime | last_pulled_from_trac | stage | status | component | type | severity | version | resolution | summary | description | owner | reporter | keywords | easy | has_patch | needs_better_patch | needs_tests | needs_docs | ui_ux |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 9093 | 2008-09-15 19:02:59 | 2014-06-30 22:34:34 | 2022-03-06 03:44:00.156209 | Accepted | new | Template system | New feature | Normal | 1.0 | Extend inclusion tag syntax to allow custom templates | Currently, inclusion tags are not very reusable since they are bound to a template at registration time. For example, the only way to customize Djagno admin's `change_list_results.html` template is to ensure your template of the same name is found first. I propose extending the inclusion tag syntax so that all inclusion tags can be called like so: {% show_results poll using "custom/results.html" %} If the "using ..." part is omitted, the template specified during registration will be used. (The keyword decided upon, 'using' in this case, is not important.) The only problem: this could break existing apps that use the keyword ('using' in this case) as a variable name. But we can make this behavior well-defined. | nobody | exogen@gmail.com | inclusion | 0 | 1 | 1 | 0 | 0 | 0 |