This is a cautionary tale in the use of umbraco.library:GetXmlNodeById(@link), with Umbraco 4.0.4.1
I found an issue on a site I was creating, where the document type was using the "Related Links" property. The page chosen was then deleted, the following code then hung, the server starting a dw20.exe process which consumed about 50% cpu.
So the XSLT was changed to the following, which worked without an issue
<!-- This returns <node> XML, use mode to ensure we do not match another template match <xsl:apply-templates select="umbraco.library:GetXmlNodeById(@link)" mode="study" />
<!-- This is not necessary, but would be called if the node id @link is not published --> <xsl:template match="error" mode="study"> <!-- Oops: <xsl:value-of select="."/> --> </xsl:template>
GetXmlNodeById caused hanging
This is a cautionary tale in the use of umbraco.library:GetXmlNodeById(@link), with Umbraco 4.0.4.1
I found an issue on a site I was creating, where the document type was using the "Related Links" property. The page chosen was then deleted, the following code then hung, the server starting a dw20.exe process which consumed about 50% cpu.
So the XSLT was changed to the following, which worked without an issue
is working on a reply...