By default each template file (*.tpl) discovered during theme scan has url matching it's location on disk:
| URL | Template |
|---|---|
| /theme_name/some_folder/some_template_name.html | /themes/theme_name/some_folder/some_template_name.tpl |
If there is a need to change url, that would lead to that template, then special block comment needs to be added in the beginning of the template:
...
If "index.tpl" template is present in any directory in theme, then it's content will be displayed automatically. Here is example:
| URL | Template |
|---|---|
| /theme_name/some_folder.html | /theme_name/some_folder.tpl OR /theme_name/some_folder/index.tpl |
| /theme_name/some_folder/index.html | /theme_name/some_folder/index.tpl |
Template Scan Problem
File system can't guarantee, that new filenames found in theme during it's scanning are always sorted in same way. That's why it's near to impossible to ensure, that "template_a.tpl" corresponding section would already be present by the time it will be found by theme scanner.
...
Quote: 1h*1.4=1.5h
Related Tasks
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|