Skip to main content

Simple XML/XSLT Breadcrumb

This post presents an example on how to transform a navigation XML with a parameterized XSLT in order to produce a simple breadcrumb.

Navigation XML

The navigation XML is produced using one of the TBBs described in earlier posts:

Navigation XML format:

<tcm:ListItems ID="tcm:1-1-4" Title="Root">
  <tcm:Item ID="tcm:1-2-4" Title="010 About Us" DisplayTitle="About Us" Url="/about-us">
    <tcm:Item ID="tcm:1-3-64" Title="010 Who are we?" DisplayTitle="Who are we?" Url="/about-us/who-are-we.html"/>
  <tcm:Item ID="tcm:1-4-64" Title="020 Contact Us" DisplayTitle="Contact Us" Url="/contact-us.html"/>

Breadcrumb XSLT

The full XSLT is available for download. This XSLT takes as parameter the current Page TCMURI as string (parameter name PageUri). It transforms the navigation XML, by identifying the tcm:Item corresponding to the current Page and starting a recursive template call to breadcrumb-item. On exiting the recursion, the current page DisplayTitle attribute is output in bold:

<xsl:stylesheet version="1.0"
    exclude-result-prefixes="fn tcm xsl">

  <xsl:output omit-xml-declaration="yes" method="html" />
  <xsl:param name="PageUri" />

  <xsl:template match="tcm:Item[@ID=$PageUri]">
    <xsl:call-template name="breadcrumb-item">
      <xsl:with-param name="current-node" select=".."/>
    <b><xsl:value-of select="@DisplayTitle"/></b>

The template breadcrumb-item calls itself recursively progressively going to the parent node of the parameterized current-node until it reaches the Root Structure Group. On exiting the recursion, it produces a series of links to the current-node Structure Group using the Url and DisplayTitle attributes and assuming the default page in the Structure Group is called index.html. The links are separated by greater-than sign ( > ).

  <xsl:template name="breadcrumb-item">
    <xsl:param name="current-node"/>
    <xsl:if test="$current-node/../@Url">
      <xsl:call-template name="breadcrumb-item">
        <xsl:with-param name="current-node" select="$current-node/.."/>
    <a href="{$current-node/@Url}/index.html"><xsl:value-of select="$current-node/@DisplayTitle"/></a> &gt;

The Transformation

In this example, I'm using the <x:transform> tag from REL Standard Tag Library (RSTL) to perform the XML / XSLT transformation.

The following code is part of the Dreamweaver TBB on a Page Template that outputs the navigation:

<c:import url="/wfaf/system/navigation.xml" var="nav-xml"/>
<c:import url="/wfaf/system/breadcrumb.xslt" var="breadcrumb-xslt"/>

<x:transform doc="nav-xml" xslt="breadcrumb-xslt">
  <x:param var="PageUri" select="@@Page.ID@@" />

Each Page published on the given Page Template will parameterize the transformation by substituting the DWT variable @@Page.ID@@ with its real value (e.g. tcm:1-2-64).

The Output

Executing the Page produces the following output:


Popular posts from this blog

A Implementation - Custom Binary Publisher

The default way to publish binaries in DD4T is implemented in class DD4T.Templates.Base.Utils.BinaryPublisher and uses method RenderedItem.AddBinary(Component) . This produces binaries that have their TCM URI as suffix in their filename. In my recent project, we had a requirement that binary file names should be clean (without the TCM URI suffix). Therefore, it was time to modify the way DD4T was publishing binaries. The method in charge with publishing binaries is called PublishItem and is defined in class BinaryPublisher . I therefore extended the BinaryPublisher and overrode method PublishItem. public class CustomBinaryPublisher : BinaryPublisher { private Template currentTemplate; private TcmUri structureGroupUri; In its simplest form, method PublishItem just takes the item and passes it to the AddBinary. In order to accomplish the requirement, we must specify a filename while publishing. This is the file name part of the binary path of Component.BinaryConten

Toolkit - Dynamic Content Queries

This post if part of a series about the  File System Toolkit  - a custom content delivery API for SDL Tridion. This post presents the Dynamic Content Query capability. The requirements for the Toolkit API are that it should be able to provide CustomMeta queries, pagination, and sorting -- all on the file system, without the use third party tools (database, search engines, indexers, etc). Therefore I had to implement a simple database engine and indexer -- which is described in more detail in post Writing My Own Database Engine . The querying logic does not make use of cache. This means the query logic is executed every time. When models are requested, the models are however retrieved using the ModelFactory and those are cached. Query Class This is the main class for dynamic content queries. It is the entry point into the execution logic of a query. The class takes as parameter a Criterion (presented below) which triggers the execution of query in all sub-criteria of a Criterio

Scaling Policies

This post is part of a bigger topic Autoscaling Publishers in AWS . In a previous post we talked about the Auto Scaling Groups , but we didn't go into details on the Scaling Policies. This is the purpose of this blog post. As defined earlier, the Scaling Policies define the rules according to which the group size is increased or decreased. These rules are based on instance metrics (e.g. CPU), CloudWatch custom metrics, or even CloudWatch alarms and their states and values. We defined a Scaling Policy with Steps, called 'increase_group_size', which is triggered first by the CloudWatch Alarm 'Publish_Alarm' defined earlier. Also depending on the size of the monitored CloudWatch custom metric 'Waiting for Publish', the Scaling Policy with Steps can add a difference number of instances to the group. The scaling policy sets the number of instances in group to 1 if there are between 1000 and 2000 items Waiting for Publish in the queue. It also sets the