I've tried this:

<xsl:template match="/">
<ul class="menuItem">
  <xsl:for-each select="umbraco.library:GetXmlNodeById(data [@alias = 'corMenuItemsID'])/corDeptMenuItem [@isDoc]">
            
    <li><a href="{umbraco.library:NiceUrl(corDeptMenuItemLink)}"><xsl:value-of select="@nodeName"/></a></li>
            
  </xsl:for-each>
</ul>
</xsl:template>

but id didn't work...
I've tried this:

<umbraco:Macro Alias="ListCustomNodeItems" menuID="[#corMenuItemsID]" runat="server"></umbraco:Macro>

with this

<xsl:template match="/">
<ul class="menuItem">
  <xsl:for-each select="umbraco.library:GetXmlNodeById(data [@alias = 'corMenuItemsID'])/corDeptMenuItem [@isDoc]">
            
    <li><a href="{umbraco.library:NiceUrl(corDeptMenuItemLink)}"><xsl:value-of select="@nodeName"/></a></li>
            
  </xsl:for-each>
</ul>
</xsl:template>

and that didn't work.  Not too sure from here.

I guess that you have the corMenuItemsID-property (or is it menuItemsID as you mentioned in your first post?) on the current page? If you do could you maybe try this out:

<xsl:template match="/">
<xsl:variable name="id" select="$currentPage/corMenuItemsID" />
<ul class="menuItem">
  <xsl:for-each select="umbraco.library:GetXmlNodeById($id)/corDeptMenuItem [@isDoc]">
            
    <li><a href="{umbraco.library:NiceUrl(corDeptMenuItemLink)}"><xsl:value-of select="@nodeName"/></a></li>
            
  </xsl:for-each>
</ul>
</xsl:template>

/Kim A

I received the following error below, do I have to create a parameter for this macro first in the Developer Section? Also I'm on 4.5.1 if this matters.

Error occured

System.Xml.Xsl.XslLoadException: The variable or parameter 'currentPage' is either not defined or it is out of scope. An error occurred at C:\inetpub\wwwroot\xslt\634181701810191856_temp.xslt(13,5).
at System.Xml.Xsl.XslCompiledTransform.LoadInternal(Object stylesheet, XsltSettings settings, XmlResolver stylesheetResolver)
at System.Xml.Xsl.XslCompiledTransform.Load(XmlReader stylesheet, XsltSettings settings, XmlResolver stylesheetResolver)
at umbraco.presentation.webservices.codeEditorSave.SaveXslt(String fileName, String oldName, String fileContents, Boolean ignoreDebugging)

Hmm...Did you not create this xslt-file through Umbraco? If you didn't could you please insert the following snippet just above the <xsl:template match="/"> :

<xsl:param name="currentPage"/>

It's a good idea to create your XSLT-files through Umbraco (especially in the beginning when you are still learning about the CMS) because you'll then alway have access to the $currentPage, umbraco.library etc. without doing anything.

/Kim A

I have that, I didn't create a Parameter for the Macro.  Is that the missing link?

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE xsl:stylesheet [ <!ENTITY nbsp "&#x00A0;"> ]>
<xsl:stylesheet
  version="1.0"
  xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
  xmlns:msxml="urn:schemas-microsoft-com:xslt"
  xmlns:umbraco.library="urn:umbraco.library" xmlns:Exslt.ExsltCommon="urn:Exslt.ExsltCommon" xmlns:Exslt.ExsltDatesAndTimes="urn:Exslt.ExsltDatesAndTimes" xmlns:Exslt.ExsltMath="urn:Exslt.ExsltMath" xmlns:Exslt.ExsltRegularExpressions="urn:Exslt.ExsltRegularExpressions" xmlns:Exslt.ExsltStrings="urn:Exslt.ExsltStrings" xmlns:Exslt.ExsltSets="urn:Exslt.ExsltSets"
  exclude-result-prefixes="msxml umbraco.library Exslt.ExsltCommon Exslt.ExsltDatesAndTimes Exslt.ExsltMath Exslt.ExsltRegularExpressions Exslt.ExsltStrings Exslt.ExsltSets ">


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

<xsl:param name="currentPage"/>

<xsl:template match="/">
<ul class="menuItem">
  <xsl:for-each select="umbraco.library:GetXmlNodeById(1321)/corDeptMenuItem [@isDoc]">
            
    <li><a href="{umbraco.library:NiceUrl(corDeptMenuItemLink)}"><xsl:value-of select="@nodeName"/></a></li>
            
  </xsl:for-each>
</ul>
</xsl:template>

</xsl:stylesheet>

That worked.  Thanks a million. May your Karma increase 100 fold.

Good to hear Kevon! Glad I could help :)

/Kim A

Kim,

I was researching a similar issue and your solution helped a bunch. Thanks!

-Wm

Also make sure your content nodes are republished if you change the propertiy names on your documenttypes.  This caused much confusion when my code was right, but didnt get the expected results.  It was due to outdated xml cache.

I'm glad you can use the answer William. It's just great when "old" answers helps people out several months after they where posted :)

/Kim A

is working on a reply...