Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
Up to version 6.1.6 I was able to get to the Content node and back down with this statement:
@Model.NodeById(-1).Descendants("Legal").First().siteCopyrightStatement
However, that doesn't seem to work in 6.2.0. The site-wide configs are stored as children of a sibling of the root, like this:
+ Content | + Site Root | + Page Nodes + Site Configs | + Config Nodes
Any idea how I can get to them now?
Can you please report this as an issue in the tracker? Sounds like it needs to be fixed before release.
It appears that the routine doesn't walk up the tree high enough. For instance:
@Library.NodeById(-1).Id
Returns "0" instead of "-1".
My hunch is that the exception with @Model is related to this.
I've logged two issues:
http://issues.umbraco.org/issue/U4-4373
http://issues.umbraco.org/issue/U4-4374
Yea i had the same thing. What i did is get to level 1 and then got siblings by doc type alias. Dont know if that helps. Other than that we have used an xpath expression to get to the root (not a fan of this approach) much prefered the (-1)
is working on a reply...
Write your reply to:
Upload image
Image will be uploaded when post is submitted
Sibling of root node in Umbraco 6.2.0 (beta)
Up to version 6.1.6 I was able to get to the Content node and back down with this statement:
However, that doesn't seem to work in 6.2.0. The site-wide configs are stored as children of a sibling of the root, like this:
Any idea how I can get to them now?
Can you please report this as an issue in the tracker? Sounds like it needs to be fixed before release.
It appears that the routine doesn't walk up the tree high enough. For instance:
Returns "0" instead of "-1".
My hunch is that the exception with @Model is related to this.
I've logged two issues:
http://issues.umbraco.org/issue/U4-4373
http://issues.umbraco.org/issue/U4-4374
Yea i had the same thing. What i did is get to level 1 and then got siblings by doc type alias. Dont know if that helps. Other than that we have used an xpath expression to get to the root (not a fan of this approach) much prefered the (-1)
is working on a reply...