Many Content Server tags use a path to reference a Content Server object. A path string is similar to a filesystem path or URL, a string of names with slashes (/) separating them. The last name is the name of the desired object, and the preceding names are the folders to traverse to find the object.
If the path begins with a slash, it is an absolute path. The search begins at the root folder of the publishing site.
path="/library/includes/music/symphony"
In this example, the site root folder is searched for a folder named “library". That folder is searched for a folder named “includes". That folder is searched for a folder named “music". That folder is searched for an object called “symphony", and that object is used by the tag.
If the path does not begin with a slash, it is a relative path. The search begins at the folder containing the template or content item in use.
path="show/public/navbar"
In this example, the current folder is searched for a folder named “show". That folder is searched for a folder named “public". That folder is searched for an object called “navbar", and that object is used by this tag.
IMPORTANT: Spaces, slashes and special characters in folder names or object names must be represented by underscores (_) in the path.
path="Related_Templates/july_and_august/summer_festival"
Folder and template names are not case sensitive. The code below is equivalent to the previous path.
path="related_templates/July_and_August/SUMMER_FESTIVAL"
The special path component ".." (two periods, often called "dot-dot") refers to the folder above the current folder:
path='../../vegetables/onions'
This example starts with the current folder, goes to the folder containing it, goes up again one folder, goes down into the folder "vegetables", and then accesses the object called "onions".
Since a root folder has no container, applying ".." to a root folder has the same effect as trying to access any folder that does not exist.
Next: Date String Formatting