Managed navigation templates / Velocity

[cmbcjason]

Hi,

We upgraded to 6.5.2 from 5.7 a while ago, but as yet haven’t converted templates to Velocity etc…still good old xml / xsl!

Plans to redesign our site means writing new page templates / managed navigation templates and although the page templates appear to be straightforward, writing new managed navigation templates in Velocity is proving a little confusing since I cannot find much documentation. I have the 6.5 developers guide and whats new in 6.5 manuals but the examples aren’t much use.

Can anyone provide any pointers / documentation / real working examples to get me started on iterating through / processing navons.

Much appreciated
Jason

[jitendra]

Have a look at the Code and Snippet Rep.

Code to generate a sitemap

Instead of manually generating a sitemap, we looked at ways to auto-generate a sitemap. This code will automatically generate a sitemap 3 levels deep and is pretty generic. You have to add a macro for each level further that you want to go on your sitemap: #macro(navlist $node $indent) #set($newindent = $indent + " ") #set($submenu = $node.getNodes("nav:submenu")) #if ($node) #foreach ($navon in $submenu) #firstlevel ($navon $indent) ##…

and

Navigation macro that accounts for non navigation content items

Standard disclaimers apply. I have removed some specific code related to checking for “special navigation items” (ie. items beginning with “–” that are specific for our implementation). This code is pretty old (once I had it working I tried not to touch it again…so there might be redundant calls…I will eventually get back to streamlining it, but right now it isn’t broken so…). Because velocity (at least the one included in 6.5 and 6.7) has a…differing… concept of variable scope, macros are nee…

are good posts that demonstrate iterating through navons…

[cmbcjason]

Cheers.

Getting something more like what appears to be navigation items now!

I’m now experimenting with calling the original xml resource along these lines

$rx.doc.getDocument("…/rxs_Navon_cas/navontree.xml" + $test) because this original resource has a load of other attributes we stored in there which determine the display / formatting of the navigation. Using this call I can get / output the raw xml but I can’t find the syntax for manipulating the returned xml. Is this possible?

Cheers
Jason