Hi Tom, 

Thanks for the reply. That got me a lot closer. I've tried both your macro and your inline xslt. They both work. The problem is the three properties that I'm trying to copy to the child pages are "Rich Text Editor" properties. so the output from both the macro and the inline xslt is the html code being displayed on the page. How can you output the content of a Rich Text Editor to the page? There is an HTML Encode function but I don't find an HTML Decode function. 

Thanks,

Hey Tom,

I really appreciate your help. You've almost got me where I wanted to go. That's working great except I have a user control based macro embedded in the "rich text editor" field. The html is showing up fine but the output from the macro isn't showing up at all.

I tried pulling the text into a variable and outputing using RenderMacroContent ( see below ) but that only renders the html on the asmx page. The code behind is never run. Do you have any idea how to get around this?

<xsl:variable name="top" select="$currentPage/ancestor-or-self::AgentNewsLibrary/sideBarTop" />
<xsl:variable name="header" select="$currentPage/ancestor-or-self::AgentNewsLibrary/sideBarHeader" />
<xsl:variable name="content" select="$currentPage/ancestor-or-self::AgentNewsLibrary/sideBarContent" />
<div class="sideinfo-top">
  <xsl:value-of select="umbraco.library:RenderMacroContent($top, $currentPage/@parentID)" disable-output-escaping="yes"/>
</div>
<div class="sideinfo-header">
  <h2><xsl:value-of select="umbraco.library:RenderMacroContent($header, $currentPage/@parentID)" disable-output-escaping="yes" /></h2>
</div>
<div class="sideinfobox">
  <xsl:value-of select="umbraco.library:RenderMacroContent($content, $currentPage/@parentID)" disable-output-escaping="yes" />
</div>

 Thanks,

Hi,

You're correct in using RenderMacroContent, but I'm pretty sure it's not possible to render a .NET Macro from an XSLT Macro...so I think you may need to find an alternative, such as embedding the .NET macro in the template instead.

You can try making sure your template has <form runat="server"> wrapped around the area where the macro is...but I still don't think that will work

-Tom

If I convert my .NET macro to an XSLT macro, will it then display correctly using the RenderMacroContent method?

Yes, the problem is rendering .NET macros from XSLT - there is no issue with rendering XSLT macros from XSLT.

-Tom

Thanks for all your help, Tom. I've marked your answer as a solution and High Fived you. 

I guess I'm going to have to start going through the xslt tutorials that I can find. Any suggestions on resources for learning XSLT, especially as it relates to umbraco?

I don't know of a good definitive tutorial, but...

- Check out the XSLT Wiki, check the links on the right for a lot of info and examples. 

- Check out pimpmyxslt.com - there is an axes visualizer that can help you understand the XPath axes, and especially check out this article - it described a different approach than most of the Umbraco examples but it really makes a lot of sense.

- There are also some examples built into Umbraco when you create a new XSLT file.

- Here is also a page describing the XML schema change in case you find some older examples.  You can also check out your XML by opening /App_Data/umbraco.config - seeing this might help make things clearer.

Other than that, just check out all the examples you can and try it out.  You can post any problems you have here and someone will surely help you out.

On a side note, remember that XSLT support is not planned for Umbraco 5, so maybe your efforts are better spent learning Razor.  Though I hate to deter anyone away from XSLT - it really is awesome ;)

On another side note, I generally try to avoid using macros in the WYSIWYG, not sure if in your case you can re-think it to include the macro in your template instead...sounds like you already have though.

-Tom

Hi, Gregg,

Maybe it could help you to learn XSLT, by looking at Umbraco.tv.

There are a few free videos about XSLT. It is certainly a good start to learn XSLT in Umbraco. That's how I got understanding XSLT in Umbraco.

http://umbraco.com/help-and-support/video-tutorials/introduction-to-umbraco.aspx?

There is a video about XSLT on about 10 minutes, I hope this can get you started understanding working with XSLT in Umbraco.

/Dennis

It's amazing how sometimes you can make something so difficult when the right way is so easy. 

I figured out how to get the properties from my parent "News Library" page to appear on each of the "News Page" pages. Including getting the embedded .NET macro to work. I simply had to add "recursive='true'" to my Umbraco:Item tags.

In my "News Library" template (Parent document) my side bar looks like this:

<div class="sideinfo-top">
      <umbraco:Item field="sideBarTop" runat="server"></umbraco:Item>
    </div>
    <div class="sideinfo-header">
      <h2><umbraco:Item field="sideBarHeader" runat="server"></umbraco:Item></h2>
    </div>
    <div class="sideinfobox">
      <umbraco:Item field="sideBarContent" runat="server"></umbraco:Item>
    </div> 

 so to output the same content in the side bar of the child pages. Including running the .NET macro imbedded in the RTE fields. I set up my "News Page" template (Child document) side bar to look like this:

<div class="sideinfo-top">
      <umbraco:Item field="sideBarTop" runat="server" recursive="true"></umbraco:Item>
    </div>
    <div class="sideinfo-header">
      <h2><umbraco:Item field="sideBarHeader" runat="server" recursive="true"></umbraco:Item></h2>
    </div>
    <div class="sideinfobox">
      <umbraco:Item field="sideBarContent" runat="server" recursive="true"></umbraco:Item>
    </div>

 Wow I made this a lot harder than it had to be. But I learned some about XSLT in the process, so it's not all bad. 

Thanks everyone for all your help.

Doh, not sure how I missed that, I think I got sidetracked by your inline XSLT comments :)  That's definately the way to go if it's all you need to do.

Also FYI, you can use the same block of code from your News Page as your News Library - recursive will try to take the value from the current page, and if it's not available move up in the tree.  So recursive="true" on the Library page would still show the same data.

-Tom

is working on a reply...