why does value of not work when inside a param or variable - XSLT

Go to solution

Press Ctrl / CMD + C to copy this to your clipboard.

Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at

Hamish 96 posts 154 karma points

Mar 25, 2010 @ 06:32

Why does value-of not work when inside a param or variable

When I use:

<xsl:variable name="list" select="$currentPage/node [string(data [@alias='umbracoNaviHide']) != '1']"/>

It works fine... but when I try to do the following:

<xsl:variable name="list">
     <xsl:choose>
        <xsl:when test="$currentPage/@nodeTypeAlias = 'Resource Listing'">
            <xsl:value-of select="$currentPage/node [string(data [@alias='umbracoNaviHide']) != '1']"/>
        </xsl:when>
        <xsl:otherwise>
            <xsl:value-of select="$currentPage/node [string(data [@alias='umbracoNaviHide']) != '1']"/>
        </xsl:otherwise>
     </xsl:choose>
</xsl:variable>

It breaks the xslt???

Does any have any insights to this?

Copy Link

skiltz 501 posts 701 karma points

Mar 25, 2010 @ 07:40

0

Where is $currentPage declared? Maybe its gone out of scope??

Copy Link
Jan Skovgaard 11280 posts 23678 karma points MVP 11x admin c-trib

Mar 25, 2010 @ 08:35

0

What kind of error message do you receive when trying to save the XSLT?

And have you tried to see if the XSLT in fact works if you check the "Skip error testing" box?

/Jan

Copy Link
Josh Reid 182 posts 258 karma points

Mar 25, 2010 @ 08:44
1
Hamish if you are finding that you get the error:

'cannot convert result tree fragment to nodeset'

Then try doing this with your variable when you need to use the list variable as for-each, etc:
```
<xsl:for-each select="msxml:node-set($list)/node">
```
While the nodeset remains intact and as a nodeset when you use inside the variable select, it becomes a result tree fragment when declared by value-of.
Copy Link
Chriztian Steinmeier 2800 posts 8790 karma points MVP 8x admin c-trib

Mar 25, 2010 @ 09:00
3
Hi Hamish,

Whenever you use value-of, the processor evaluates the result as a string, whereas select returns a nodeset. If you need to conditionally select the node(s) for a variable, you need to use copy-of instead of value-of, but then you're actually getting a "result tree frament" (as Josh mentions) - you can convert that to a nodeset using the msxml:node-set() function (remember to declare the msxml prefix - the standard XSLT templates does that automatically). So domething like this:
```
<xsl:variable name="list">
     <xsl:choose>
        <xsl:when test="$currentPage/@nodeTypeAlias = 'Resource Listing'">
            <xsl:copy-of select="$currentPage/node[not(data[@alias = 'umbracoNaviHide'] = 1)]"/>
        </xsl:when>
        <xsl:otherwise>
            <xsl:copy-of select="...something else..."/>
        </xsl:otherwise>
     </xsl:choose>
</xsl:variable>

...

<xsl:for-each select="msxml:node-set($list)/node">
```
/Chriztian
Copy Link
Josh Reid 182 posts 258 karma points

Mar 25, 2010 @ 09:30

0

Well put Chriztian, I was probably a tad brief before...

Mental note to write up more fully in the future ;)

Copy Link
Hamish 96 posts 154 karma points

Mar 25, 2010 @ 22:08

0

Thanks guys for your help and the insight of how value-of actually works..

That info helped save my sanity...

Copy Link
is working on a reply...

Please Sign in or register to post replies

Flag this post as spam?

Why does value-of not work when inside a param or variable

'cannot convert result tree fragment to nodeset'