Blacklists a template for a theme. This means that the template service will not consider this theme and path combination the next time it is prompted to check for its existence

Compiles the content be eagerly searching for flags/directives. The static content is also placed into an object. Whether static or a flag, an object is created and pushed into an array. Each object has two properties: "type" that describes the type of template part it is (static, flag). "val" the string value of the part.

Retrieves the content templates that are available for use to render Articles and pages.

Creates an instance of Template service based

Retrieves the path to a template file based on the assumption that the provided path is relative to the pencilblue/plugins/[themeName]/templates/ directory.

Retrieves the default path to a template file based on the assumption that the provided path is relative to the pencilblue/plugins/pencilblue/templates/ directory.

returns the value associated with a registered local key(flag)

Retrieves the raw template based on a priority. The path to the template is derived from the specified relative path and the following order of directories:

1. The theme provided by "getTheme" if not null
2. The globally set active_theme
3. Iterates over the list of active plugins looking for the template
4. The system template directory

Retrieves the content template names and locations for the active theme.

Retrieves the prioratized theme

Called when the processing engine encounters a non-sub-template flag. The function delegates the content transformation out to either the locally or globally registered function. In the event that a value was registered and not a function then the value is used as the second parameter in the callback. During template re-assembly the value will be converted to a string.

When a sub-template flag is encountered by the processing engine this function is called to parse the flag and delegate out the loading and processing of the sub-template.

Sets up the default flags required for the template service, including the flags that were previously considered to be global but now requires to be instanced with the TemplateService

Determines if the content provided is equal to the flag

Checks to see if a template has been blacklisted

Loads a template file along with any encountered sub-template files and processes any flags. The call back provides any error encountered and a second parameter that is the transformed content.

Scans the template for flags. The callback provides any error and a second parameter that is the populated template with any registered flags replaced.

Called when a flag is encountered by the processing engine. The function is responsible for delegating out the responsibility of the flag to the registered entity. Some flags are handled by default (although they can always be overriden locally or globally). The following flags are considered "baked in" and will be handled automatically unless overriden:

• ^loc_xyz^ - A localization flag. When provided, the Localization instance will have its "get" function called in an attempt to retrieve the properly translated value for the key (the part betwee "^loc_" and the ending "^").
• ^tmp_somedir=someotherdir=templatefileminusext^ - Specifies a sub-template that should be loaded processed. The file is expected to have a .html extension.

Registers a value or function for the specified

Registers a value or function for the specified

Registers a model with the template service. It processes each key/value pair in the object and creates a dot notated string registration. For the object { key: 'value' } with a model name of "item" would result in 1 local value registration in which the key would be "item.key". If no model name existed the registered key would be: "key". The algorithm fails fast. On the first bad registeration the algorithm stops registering keys and returns. Additionally, if a bad model object is pass an Error object is thrown.

When a flag is encountered that is not registered with the engine the handler is called as a fail safe unless there is a locally registered handler. It is expected to return a string that will be put in the place of the flag.

Sets the option that when true, instructs the engine to inspect the content provided by a flag for more flags. This is one way of providing iterative processing of items. See the sample plugin for an example.

Sets the prioritized theme to use when loading templates

When a flag is encountered that is not registered with the engine the handler is called as a fail safe. It is expected to return a string that will be put in the place of the flag.