Could you please post the entire XSLT code you're currently fiddling with? And could you also let us know what XSLT error you get on the frontend?
Sounds like you're using the xslt editor in Umbraco. I'll recommend that you use an external editor like visual studio or sublime text instead.
If you add ?umbdebugshowtrace=1 to the url when you visit the page where your rendering is failing you will perhaps get a more detailed explanation of the error. It would be nice if you would post that as well.
getting a specfic value while looping through a node set
I'm looping through a nodeset.
If I print out the value of each node inside the for loop, it looks like this:
<relation typeId="7" typeName="AllPrograms" createDate="5/8/2013 10:22:20 PM" parentId="1146" childId="1267"><comment/><node id="1267" parentID="1137" level="3" writerID="2" sortOrder="1" createDate="2012-12-01T01:21:35" nodeName="Acid Jazz" path="-1,1087,1137,1267" />
While inside this loop, all that I want to do is check the value of "typeName"
For some reason, I can't get to it.
I've tried:
But either I get blanks or the page errors on rendering (not during .xslt save)
It puzzles me because if I can do this:
and I can get the node represented by childid 1267 above.
However, when I do this:
I just get an error upon rendering in the page (not during save)
What am I doing wrong?
Hi Jacob
Could you please post the entire XSLT code you're currently fiddling with? And could you also let us know what XSLT error you get on the frontend?
Sounds like you're using the xslt editor in Umbraco. I'll recommend that you use an external editor like visual studio or sublime text instead.
If you add ?umbdebugshowtrace=1 to the url when you visit the page where your rendering is failing you will perhaps get a more detailed explanation of the error. It would be nice if you would post that as well.
Looking forward to hearing from you.
/Jan
Thx, I figured it out.
Thanks for the external editor suggestions.
Also, I forgot about the umbdebugshowtrace, I will use that.
Even though I solved my own problem, part of the problem was my not understanding the difference between xsl:copy-of vs. xsl:value-of.
This reference quickly set me straight and might be helpful for someone else:
http://dev.ektron.com/blogs.aspx?id=10472
is working on a reply...