Mercurial > p > roundup > code
comparison doc/customizing.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 | 9e8d8cd49f40 |
| children | 882fa4d9bead |
comparison
equal
deleted
inserted
replaced
| 5153:e9801faebbe4 | 5154:f608eeecf638 |
|---|---|
| 92 Database directory path. The path may be either absolute or relative | 92 Database directory path. The path may be either absolute or relative |
| 93 to the directory containig this config file. | 93 to the directory containig this config file. |
| 94 | 94 |
| 95 templates -- ``html`` | 95 templates -- ``html`` |
| 96 Path to the HTML templates directory. The path may be either absolute | 96 Path to the HTML templates directory. The path may be either absolute |
| 97 or relative to the directory containig this config file. | 97 or relative to the directory containing this config file. |
| 98 | 98 |
| 99 static_files -- default *blank* | 99 static_files -- default *blank* |
| 100 Path to directory holding additional static files available via Web | 100 Path to directory holding additional static files available via Web |
| 101 UI. This directory may contain sitewide images, CSS stylesheets etc. | 101 UI. This directory may contain sitewide images, CSS stylesheets etc. |
| 102 and is searched for these files prior to the TEMPLATES directory | 102 and is searched for these files prior to the TEMPLATES directory |
| 1482 | 1482 |
| 1483 Neither b. or e. use templates and stop before the template is | 1483 Neither b. or e. use templates and stop before the template is |
| 1484 determined. For other contexts the template used is specified by the | 1484 determined. For other contexts the template used is specified by the |
| 1485 ``@template`` variable, which defaults to: | 1485 ``@template`` variable, which defaults to: |
| 1486 | 1486 |
| 1487 - only classname suplied: "index" | 1487 - only classname supplied: "index" |
| 1488 - full item designator supplied: "item" | 1488 - full item designator supplied: "item" |
| 1489 | 1489 |
| 1490 | 1490 |
| 1491 The "home" Context | 1491 The "home" Context |
| 1492 ------------------ | 1492 ------------------ |
| 1796 | 1796 |
| 1797 http://your.tracker.example/tracker/issue?@template=test | 1797 http://your.tracker.example/tracker/issue?@template=test |
| 1798 | 1798 |
| 1799 and it won't affect your users using the "issue.item" template. | 1799 and it won't affect your users using the "issue.item" template. |
| 1800 | 1800 |
| 1801 You can also put templates into a subdirectory of the template | |
| 1802 directory. So if you specify:: | |
| 1803 | |
| 1804 http://your.tracker.example/tracker/issue?@template=test/item | |
| 1805 | |
| 1806 you will use the template at: ``test/issue.item.html``. If that | |
| 1807 template doesn't exit it will try to use | |
| 1808 ``test/_generic.item.html``. If that template doesn't exist | |
| 1809 it will return an error. | |
| 1801 | 1810 |
| 1802 How the templates work | 1811 How the templates work |
| 1803 ---------------------- | 1812 ---------------------- |
| 1804 | 1813 |
| 1805 | 1814 |