Mercurial > p > roundup > code
diff doc/upgrading.txt @ 5154:f608eeecf638
issue2550891: Allow subdir in template value. Anthony (antmail)
requested the ability to put templates into subdirectories. So
the issue class can accept @template=issues/item to get the
html/issues/issue.item.html template.
Inlcude a test case for missing and existing (tal) templates.
Also include a test that fails path traversal check.
Add mention of subdiectoy use to customizing.txt along with some
spelling fixes and ^M removal.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Fri, 22 Jul 2016 15:19:40 -0400 |
| parents | d16ba6e6624b |
| children | 882fa4d9bead |
line wrap: on
line diff
--- a/doc/upgrading.txt Wed Jul 20 22:30:35 2016 -0400 +++ b/doc/upgrading.txt Fri Jul 22 15:19:40 2016 -0400 @@ -173,6 +173,19 @@ devel templates and has not changed the html/_generic.404.html file, you can copy in the new file to get this additional functionality. +Organize templates into subdirectories +-------------------------------------- + +The @template parameter to the web interface allows the use of +subdirectories. So a setting of @template=view/view for an issue would +use the template in the tracker's html/view/issue.view.html. Similarly +for a caller class, you could put all the templates under the +html/caller directory with names like: html/caller/caller.item.html, +html/caller/caller.index.html etc. You may want to symbolically link the +html/_generic* templates into your subdirectory so that missing +templates (e.g. a missing caller.edit.html template) can be satisfied +by the _generic.edit.html template. + Schema change to allow "Show Unassigned" issues link to work for Anonymous user -------------------------------------------------------------------------------