Skip to main content

Simple XML/XSLT Navigation

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

Navigation XML

The navigation XML is produced using one of the TBBs described in my 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>
  <tcm:Item ID="tcm:1-4-64" Title="020 Contact Us" DisplayTitle="Contact Us" Url="/contact-us.html"/>
</tcm:ListItems>

Navigation 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 Structure Group parent node of the current Page:

<xsl:stylesheet version="1.0"
    xmlns:fn="http://www.w3.org/2005/xpath-functions"
    xmlns:tcm="http://www.tridion.com/ContentManager/5.0"
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    exclude-result-prefixes="fn tcm xsl">

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

  <xsl:param name="PageUri" />

  <xsl:template match="/">
    <xsl:apply-templates/>
  </xsl:template>

  <xsl:template match="tcm:Item[tcm:Item/@ID=$PageUri]">
    <xsl:call-template name="output-parent-sg">
      <xsl:with-param name="parent-node" select="."/>
    </xsl:call-template>

    <xsl:call-template name="output-sg">
      <xsl:with-param name="parent-node" select="."/>
    </xsl:call-template>

    <xsl:call-template name="output-page">
      <xsl:with-param name="parent-node" select="."/>
    </xsl:call-template>

    <xsl:apply-templates/>
  </xsl:template>

The template continues to apply three transformations:
  • output-parent-sg: outputs a link to the parent Structure Group relative to the current Structure Group, if the parent is not the Root Structure Group. The link URL assumes the default page in the parent Structure Group is index.html. The link text is the value of the parent's attribute DisplayTitle;
  <xsl:template name="output-parent-sg">
    <xsl:param name="parent-node"/>
    <xsl:if test="$parent-node/../@Url">
      <ul>
        <li>
          &lt;-- <a href="{$parent-node/../@Url}/index.html"><xsl:value-of select="$parent-node/../@DisplayTitle"/></a>
        </li>
      </ul>
    </xsl:if>
  </xsl:template>
  • output-sg: outputs a list of links to all sub-Structure Groups relative to the current Structure Group;
  <xsl:template name="output-sg">
    <xsl:param name="parent-node"/>
    <ul>
      <xsl:for-each select="$parent-node/tcm:Item[fn:ends-with(string(@ID),'-4')]">
        <xsl:sort select="@Title"/>
        <li>
          <a href="{@Url}/index.html"><xsl:value-of select="@DisplayTitle"/></a> --&gt;
        </li>
      </xsl:for-each>
    </ul>
  </xsl:template>
  • output-page: outputs a list of links to all Pages within the current Structure Group. The current Page ($PageUri) is highlighted in bold and it is not rendered as link;
  <xsl:template name="output-page">
    <xsl:param name="parent-node"/>
    <ul>
      <xsl:for-each select="$parent-node/tcm:Item[fn:ends-with(string(@ID),'-64')]">
        <xsl:sort select="@Title"/>
        <li>
          <xsl:choose>
            <xsl:when test="@ID=$PageUri">
              <b><xsl:value-of select="@DisplayTitle"/></b>
            </xsl:when>
            <xsl:otherwise>
              <a href="{@Url}"><xsl:value-of select="@DisplayTitle"/></a>
            </xsl:otherwise>
          </xsl:choose>
        </li>
      </xsl:for-each>
    </ul>
  </xsl:template>
</xsl:stylesheet>

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/navigation.xslt" var="nav-xslt"/>

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

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:


Labels:

Comments

Post a Comment

Popular posts from this blog

Scaling Policies

By
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
Post a Comment
Read more

Toolkit - Dynamic Content Queries

By
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
Post a Comment
Read more

Running sp_updatestats on AWS RDS database

By
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: https://dba.stackexchange.com/questions/145982/sp-updatestats-vs-update-statistics I stumbled upon the following post from 2008 (!!!), https://social.msdn.microsoft.com/Forums/sqlserver/en-US/186e3db0-fe37-4c31-b017-8e7c24d19697/spupdatestats-fails-to-run-with-permission-error-under-dbopriveleged-user , 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
1 comment
Read more