Hi Craig,

Here's the basics of setting that up:

<?xml version="1.0" encoding="utf-8" ?>
<xsl:stylesheet
    version="1.0"
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    xmlns:umb="urn:umbraco.library"
    exclude-result-prefixes="umb"
>

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

    <xsl:param name="currentPage" />
    <xsl:variable name="siteRoot" select="$currentPage/ancestor-or-self::*[@level = 1]" />

    <xsl:template match="/">
        <!-- Find and process the Test node --> <xsl:apply-templates select="$siteRoot//*[@nodeName = 'Test']" />
    </xsl:template>

    <!-- Generic template for any Umbraco Document Node  -->
    <xsl:template match="*[@isDoc]">
        <div>
            <!-- Usually an RTE field, so need to disable output escaping -->
            <xsl:value-of select="bodyText" disable-output-escaping="yes" />
        </div>
    </xsl:template>

</xsl:stylesheet>

The double slash is a shortcut for the descendant:: axis which basically runs through the entire structure (here, below $siteRoot) so if you have more than one called "Test", they will all be processed.

If you know roughly where it's located, a more specific XPath will perform better, especially in a large tree, e.g.:

<xsl:apply-templates select="$siteRoot/Pages/Textpage[@nodeName = 'Test']" />

Let's say you had 5 childnodes of $siteRoot - then you've just saved the processor the hassle of going down 4 of them, by specifying the "Pages" child.

/Chriztian

Hi Chriztian,

That's exactly what I wanted. Thanks a million :)

Craig

is working on a reply...