StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p><strong>UPDATE</strong>: @deniz_seaside, please give us the XML document and also see it for the first time.</p> <p>Then, probably, you'll write your transformation again, this time much better.</p> <p><strong>Here is how to obtain the XML document that you don't have</strong>: just apply this transformation to this unknown document:</p> <pre><code> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output omit-xml-declaration="yes" indent="yes"/> <xsl:template match="node()|@*"> <xsl:copy> <xsl:apply-templates select="node()|@*"/> </xsl:copy> </xsl:template> </xsl:stylesheet> </code></pre> <p><strong>Or even shorter</strong>:</p> <pre><code><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output omit-xml-declaration="yes" indent="yes"/> <xsl:template match="/"> <xsl:copy-of select="."/> </xsl:template> </xsl:stylesheet> </code></pre> <hr> <pre><code><xsl:for-each select="$currentPage/node [string(data [@alias='umbracoNaviHide']) != '1']"> <album lgPath="http://localhost" tnPath="http://localhost" title="{data[@alias = 'albumTitle']}" description="{data[@alias = 'albumDescription']}" tn="http://localhost"> <xsl:for-each select="node"> </code></pre> <p>The second <code><xsl:for-each></code> is most likely incorrect. It will select for processing all nodes named <code>node</code> of the current node, which is also named <code>node</code>. Usually a node named <code>node</code> doesn't have children named <code>node</code>, too.</p> <p>The solution is to remove the second <code><xsl:for-each></code> instruction and leave its content ( body) in the body of the first <code><xsl:for-each></code> instruction.</p> <p><strong>Do note</strong>:</p> <ol> <li><p><strong>As you haven't provided any source XML document, your problem is most likely duew to the bad weather</strong>.</p></li> <li><p><strong>Never use the name <code>node</code></strong> for an element, attribute or processing-instruction. You are increasing the chances of getting confused and committing errors by a factor of 1000.</p></li> </ol>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload