RunwayNavigation XSLT and specifying the correct parent or root node
On: Umbraco 4.6.1
Context: Content view:
Content > Home > [ 2 -tier content ] > Blog > [ using blogs4umbraco structure ]
I am using a modified RunwayNavigation XSLT that works great from the "Home" node. However, I'd like to use the same XSLT from within the "Blog" peer node. The RN XSLT dutifully runs out the nav structure of "Blog" but I want the Home section pages output there.
I'm sure this is simple, but how do I tell it to point to "Home" and not "Blog" ?
Alright, my taciturn friends, maybe this helps? The Runway Navigation XSLT is using this variable:
<xsl:param name="parent"/>
Which, I'm guessing, determines the "start" point for the node/navigation traversal/recursion. If I could set that to, say "1056" (the id of my home node) but I'm flummoxed on where to start?
You want the Blog node to be a part of the main navigation or what do you want? Or you just want a link to the Home node in the navigation of the Blog nodes? I don't think I quite undestand what you're trying to achieve.
I want this same navigational output from within the "Blog" section, the sibiling of "Home" That is to say, that it's not using the top-most node, i.e., "Blog" to render the menu.
Can't you just put the Blog node under the Home node? This would create the same menu as if you where standing on the Testimonials-node, the Product node or whatever.
Yea, I know. Yesterday, I was getting an error when I tried to move my blog parent node. Today, I'm not. Blog is now a direct descendent of "Home" with the boolean to be hidden from the main nav. Yea, that solves my problem. Much thanks!
If you insisted to keep the structure the other way we could have solved the issue as well, but moving the Blog node sounds like a much better solution in my ears :)
RunwayNavigation XSLT and specifying the correct parent or root node
On: Umbraco 4.6.1
Context: Content view:
Content
> Home
> [ 2 -tier content ]
> Blog
> [ using blogs4umbraco structure ]
I am using a modified RunwayNavigation XSLT that works great from the "Home" node. However, I'd like to use the same XSLT from within the "Blog" peer node. The RN XSLT dutifully runs out the nav structure of "Blog" but I want the Home section pages output there.
I'm sure this is simple, but how do I tell it to point to "Home" and not "Blog" ?
Thanks!
Alright, my taciturn friends, maybe this helps? The Runway Navigation XSLT is using this variable:
<xsl:param name="parent"/>
Hi Kyle
You want the Blog node to be a part of the main navigation or what do you want? Or you just want a link to the Home node in the navigation of the Blog nodes? I don't think I quite undestand what you're trying to achieve.
/Kim A
Kim,
Thanks for asking.
All children nodes of "Home" that run the runway nav XSLT produce, say:
Home:
-->Product
----->Widgets
----->Wadgets
----->Wonkgets
-->Services
----->Widget Enhancement
----->Widget Retirement
----->Widget Removal
-->Testimonials
----->Joe Smith
----->tallulah bankhead
I want this same navigational output from within the "Blog" section, the sibiling of "Home" That is to say, that it's not using the top-most node, i.e., "Blog" to render the menu.
Does that make sense?
Can't you just put the Blog node under the Home node? This would create the same menu as if you where standing on the Testimonials-node, the Product node or whatever.
/Kim A
Yea, I know. Yesterday, I was getting an error when I tried to move my blog parent node. Today, I'm not. Blog is now a direct descendent of "Home" with the boolean to be hidden from the main nav. Yea, that solves my problem. Much thanks!
Great to hear Kyle.
If you insisted to keep the structure the other way we could have solved the issue as well, but moving the Blog node sounds like a much better solution in my ears :)
/Kim A
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.