Something like this should work, in an XSLT macro:

<xsl:if test="string($currentPage/data [@alias='myLinkProperty']) != ''">
 <a>
  <xsl:attribute name="href"><xsl:value-of select="umbraco.library:NiceUrl($currentPage/data [@alias='myLinkProperty'])"/></xsl:attribute>
  Click Me
 </a>
</xsl:if>

Or if you're using 4.5, it would be $currentPage/myLinkProperty instead

I am using 4.5 and was using the old format.  Using $currentPage/myLinkProperty and it seems to work fine.  Now, I cannot get the node name.  Using <xsl:value-of select="@nodeName"/> in place of Click Me causes nothing to display.

Try <xsl:value-of select="$currentPage/@nodeName"/>  :)

That give me the node name of the current page instead of the node name of the targeted page.

Oh, sorry, wasn't thinking.  To get properties from the targeted page you can use GetXmlNodeById:

<xsl:value-of select="umbraco.library:GetXmlNodeById($currentPage/myLinkProperty)/@nodeName"/>

Awesome, another step closer.  Now, all I need is to make it recursive so every page based upon that document type defaults to the value set in the master doc type.

This *should* get the value recursively:

<xsl:value-of select="$currentPage/ancestor-or-self::* [@isDoc and myLinkProperty != '']/myLinkProperty"/>

Make sure to update this Xpath statement in your IF, href attribute and inside the NiceUrl function

Ok, I think I have my final solution so I thought I would share.  I ran into another issue... I wanted the property from the currentPage to take priority. I only wanted to go the the ancestor property if the currentPage property is empty.  With ancestor-or-self you cannot control that.  So I check for currentPage first.

 <xsl:choose>
  <xsl:when test="string($currentPage/hotLink) != ''">
   <a>
    <xsl:attribute name="href">
     <xsl:value-of select="umbraco.library:NiceUrl($currentPage/hotLink)"/>
    </xsl:attribute>
    <xsl:value-of select="umbraco.library:GetXmlNodeById($currentPage/hotLink)/@nodeName"/>
   </a>
  </xsl:when>

  <xsl:when test="string($currentPage/ancestor::* [@isDoc and hotLink!= '']/hotLink) != ''">
   <a>
    <xsl:attribute name="href">
     <xsl:value-of select="umbraco.library:NiceUrl($currentPage/ancestor::* [@isDoc and hotLink!= '']/hotLink)"/>
    </xsl:attribute>
    <xsl:value-of select="umbraco.library:GetXmlNodeById($currentPage/ancestor::* [@isDoc and hotLink!= '']/hotLink)/@nodeName"/>
   </a>
  </xsl:when>

  <xsl:otherwise>

  </xsl:otherwise>
 </xsl:choose>

Hi Connie

Why not just use a recursive macro property?

Just define a property on your macro, then set it's value when you embed it like so

Umbraco will automaticaly check the current page, then it's ancestors untill it finds a value, and then pass it into your macro.

Matt

UPDATE (The example got stripped from my phone)

<umbraco:macro alias="mymacroalias" mypropertyalais="[$mydocpropertyalias]" runat="server" />

Ah, forgot all about that. 

If you prefer your existing solution I think you can get the recursion behaving like you want by adding position() = 1 to the Xpath conditions, according to this post anyway

Matt's solution may be easier though :)

-Tom

Matt,

Ok, so if I understand, the idea is to pass a property from the page to the macro and then use that value in my macro?  I sort of get it...

Yes!  Now I know how to pass in values to a macro, which will be helpful for some other tasks.  Below is my final XSLT code which is much simpler and cleaner than what I had before.  One thing, why do I always have to check for an empty value?  Does that just satisfy the editor?

<xsl:variable name="theHotLink" select="/macro/hotLink"/>

<xsl:template match="/">

  <xsl:if test="string($theHotLink) != ''">
    <a>
      <xsl:attribute name="href">
        <xsl:value-of select="umbraco.library:NiceUrl($theHotLink)"/>
      </xsl:attribute>
      <xsl:value-of select="umbraco.library:GetXmlNodeById($theHotLink)/@nodeName"/>
    </a>
  </xsl:if>

Hi Connie,

Checking the string length is good practise, and prevents the value from being used if it is empty, which could cause an XSLT template error otherwise.

Matt

Hi,

I have created a Master template which displays a text string and related links using XSLT/Macro(Using Umbraco 4.5).When I try to access it from my child page,it displays the textstring but does not display anything for relatedlinks.Can anyone help me with this?

Thanks,

Brady

is working on a reply...