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

Running sp_updatestats on AWS RDS database

Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: I stumbled upon the following post from 2008 (!!!), , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as

Content Delivery Monitoring in AWS with CloudWatch

This post describes a way of monitoring a Tridion 9 combined Deployer by sending the health checks into a custom metric in CloudWatch in AWS. The same approach can also be used for other Content Delivery services. Once the metric is available in CloudWatch, we can create alarms in case the service errors out or becomes unresponsive. The overall architecture is as follows: Content Delivery service sends heartbeat (or exposes HTTP endpoint) for monitoring Monitoring Agent checks heartbeat (or HTTP health check) regularly and stores health state AWS lambda function: runs regularly reads the health state from Monitoring Agent pushes custom metrics into CloudWatch I am running the Deployer ( installation docs ) and Monitoring Agent ( installation docs ) on a t2.medium EC2 instance running CentOS on which I also installed the Systems Manager Agent (SSM Agent) ( installation docs ). In my case I have a combined Deployer that I want to monitor. This consists of an Endpoint and a

Debugging a Tridion 2011 Event System

OK, so you wrote your Tridion Event System. Now it's time to debug it. I know this is a hypothetical situtation -- your code never needs any kind of debugging ;) but indulge me... Recently, Alvin Reyes ( @nivlong ) blogged about being difficult to know how exactly to debug a Tridion Event System. More exactly, the question was " What process do I attach to for debugging even system code? ". Unfortunately, there is no simple or generic answer for it. Different events are fired by different Tridion CM modules. These modules run as different programs (or services) or run inside other programs (e.g. IIS). This means that you will need to monitor (or debug) different processes, based on which events your code handles. So the usual suspects are: dllhost.exe (or dllhost3g.exe ) - running as the MTSUser is the SDL Tridion Content Manager COM+ application and it fires events on generic TOM objects (e.g. events based on Tridion.ContentManager.Extensibility.Events.CrudEven