Hi,

Can you do this call without the quotes, as GetXmlNodeById expects an integer parameter.

<xsl:variable name="physiciansNode" select="umbraco.library:GetXmlNodeById(1130)"/>

Cheers,

/Dirk

I have tried that too, and the extension puts it in as string, but I did try it both ways.

Have you checked that data/umbraco.config xml file contains the node? I know that if the template is outputting the id then the raw xml must be ok.

Also, try outputting the cached xml directly to the screen, and then check it for the id too.

<textarea cols=50 rows="50">
   <xsl:copy-of select="umbraco.library:GetXmlAll()"/>
</textarea

What happens if you access the node via xslt rather than api calls?

<xsl:value-of select="$currentPage/ancestor-or-self::node//node{@id='1130'/@nodeName"/>

Does the page/node name get rendered on screen?

Chris,

It was not showing up in the GetXmlAll call.  I don't know why.  I know that this particular node does not have an associated template, and neither does its parent, I don't have to have a template to get it into the xml do I?

Thanks for the additional info.

Hmmm, is it a permissions issue on the server to that data file you mentioned earlier maybe?

I there a solution for this problem? I'm having the same.

Ron

Ron,

The problem in my respect was a file permission problem on the umbraco.config file in the config directory.  This is apparently where the site's xml is cached and it is what appears to be used by the admin app.

If that's true, there will be hell to pay :p
But I can't imagine that is the case.

I'll let you know tomorrow.

Ron

It seems the security is set as it should be.

But no luck so far.

Ron

is working on a reply...