Attribute - path

Set this attribute to the location of the template for which the contents should be included. If the template path begins with // then the template path will be considered relative to the compileTemplatePath that you set in the project configuration. If the path is preceded by / then the template will be retrieved relative to the root of the filesystem. Last, if neither of the former two cases are true then the path will be treated as being relative to the last nested template path. You should make sure that read permission is set for the appropriate owners at this location.

The recent addition of the Content Manager Service has added the option to load content via any number of different methods. To specify the exact method you must use the following styles for your path:

file:////mainLayout.template
sql:///templates/main.template

There are three parts to the examples and specifically for the first example: the type specifier file, the separator ://, and the path //mainLayout.template. If you do not specify the type portion of the path, then the value configured in the $GLOBALS['interJinn']['contentDefaultType'] property will be used to determine the type. If this property has not been set then file is assumed.