A special CMS hook called Tokenizing allows custom Global Modules to intercept tokens in markup and optionally replace them based on special logic before it is rendered to a web site visitor. Token strings take the format {% TOKENNAME } and by default can be placed inside:
The CMS has built-in support for the following tokens:
Name | Format | Summary |
GlobalValues | {% GlobalValues["GROUP"]["KEY"] } |
Replaced with the Global Value value found at Site Settings > Global Values.
|
ItemField | {% ItemField["ITEMID"]["FIELD"] } |
Replaced with the specified item's predefined field. If the item is not found, then an empty string is used as a replacement.
|
ItemSingleValue | {% ItemSingleValue["ITEMID"]["PATH"] } |
Replaced with the value in a specified item found at a path. If the item or the value located at the path is not found, then an empty string is used as a replacement.
|
Item | {% Item["ITEMID"] } |
Replaced with the specified item as rendered by its Module. The item's includes are registered. If the item is not found or inactive then an empty string is used as a replacement.
|
Module | {% Module["MODULEID"] } |
Replaced with the specified module rendering. This only applies to Modules that are not item-based.
|
Custom Global Modules can be written to support additional tokens.