to get which parent node you're under

<xsl:if test="$currentPage::ancestor-or-self/*/@id = 1000"/> - double check the syntax, but that's the general idea

you can't call another macro from an xslt macro per se, but if you add a reference to another xslt file, you can call templates that are in the referenced xslt file

And you CAN call another macro from xslt, but only if that macro also references a xslt file (not a user control). use umbraco.library:RenderMacro(). Anyway, Euan's suggestion of using includes is preferred in this case.

Cheers,

/Dirk

Wow, you learn something every day :) Is using includes faster than using umbraco.library:RenderMacro()?

i have no stats on performance of using includes vs RenderMacro, so wouldn't know. Anyway, think includes is a nicer solution compared to using RenderMacro. Keep one thing in mind (unless that's been solved, it used to be an issue), is if you're changing a xslt that includes another xslt, you need to save both (also the included xslt) before you'd see any changes...

Cheers,

/Dirk

Wow thanks for both the solutions !

Both worked like a charm :)

Hi andi8u - another approach:

I usually do this in multilingual setups:

<xsl:param name="currentPage" />
<xsl:variable name="siteRoot" select="$currentPage/ancestor-or-self::Website" />

- If you don't use a specific Document Type for the root of each site, you can just check the level attribute:

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

Now you can ask:

<xsl:if test="$siteRoot/@nodeName = 'en'">
    <!-- do stuff in english -->
</xsl:if>

or you can just do language-specific stuff:

<xsl:for-each select="$siteRoot[@nodeName = 'de']//NewsItem">
    <!-- Do something in german -->
</xsl:for-each> 

/Chriztian

is working on a reply...