XML attributes

<root>

loggedin = "#session.authAdmin#"
circuit = "#fusebox.circuit#"
fuseaction = "#fusebox.fuseaction#"
itmId = "#val(attributes.itm_id)#"
index = "#GetFileFromPath(GetBaseTemplatePath())#" 

<item>

id = "#itm_id#"
name = "#itm_name#"
caption = "#itm_caption#"
displayChildren = "#itm_displayChildren#"
createDate = "#itm_createDate#"
lastModified = "#itm_lastModified#"
publish = "#itm_publish#"
publishDate = "#itm_publishDate#"
expireDate = "#itm_expireDate#"
isArchived = "#itm_isArchived#"
directLink = "#itm_directLink#"
left = "#itm_left#"
right = "#itm_right#"
<!--- convenience properties for hyperlinks --->
href="#getHref(itm_id,itm_directLink)#"
namehref="#getHref(itm_name,itm_directLink)#"
<!--- insert assigned properties from set_propertiesList as attributes --->
#getSiteSpecificProperties(itm_properties)#

displayChildren

displayChildren contains a setting that determines if and how first-level descendants of an item are displayed at the page of the current item:

• 0: not at all;
• 1: only a link;
• 2: a link and a summary;
• 3: complete contents (not summary, no linking).

You are strongly encouraged to follow these rules in your XSLT sheet, since they are hard-coded in the CMS interface, but you're not obliged to do so.

href

href is constructed in the following manner:

1. If directLink is not empty and starts with 'http': href = directLink (outside link);
2. if directLink is not empty and doesn't contain 'http' href refers to itm_id. directLink is appended to CGI.query_string. Use this to call a module by setting directLink to 'fuseaction=[circuit].[action]';
3. when directLink is empty href just refers to itm_id, which is the default situation.

It is not necessary to use the href attribute in XSLT transformations. The same, or another, logic could also be implemented in the XSLT sheet itself. Therefore it is called a convenience property. It may keep your XSLT compact.

namedhref is similar, but uses itm_name instead of itm_id, which leads to nicer looking urls, but which is also handy for linking to pages from outside the system, or from a module (in case you need to hard-code the links).

site specific properties

Site specific properties are boolean properties (eg. newsitem = 1) that define qualities an item may or may not have. Which properties there are to choose from, depends on the value of the PROPERTIESLIST field in settings.ini. In the CMS edit screen they appear as checkboxes. These properties provide an excellent means to select cross-sections from the items collection in the XSLT sheet, for instance to display the summary of an item at the homepage.

<summary>

<![CDATA[#itm_summary#]]>

<contents>

<![CDATA[#itm_contents#]