Hello RedDots, here is some foreach render tag processing to get around the issues listed above.
<rant> It seems that, much to my dismay, RedDot only supports one navigation 'list' per project. I thought, and was told, that each list could be navigated seperatly, instead it appears that all pages are added to the cumalitive navigation structure, regardless of separate lists. </rant> We want to continue using Nav Manager for the most part but have a Top Graphic navigation system that should display separate navigation structures depending on context. The render tag "foreach" syntax works well thus far but I'm waiting to see what other surprises I have created for myself. Any comments from folks that have tried similar constructs? Note that all pages still have to be master pages with a list for navigation. <reddot:cms> <foreach itemname="item" object="Context:CurrentIndex.GetPathArray() [Int:0].SubIndexes"> <output type="string"> <htmltext> <li> <a href="<%!! Store:item.GetUrl() !!%>"> <img src="<%!! Store:item.Page.Elements.GetElement(img_SectionImage).GetHtml() !!%>" alt="<%!! Store:item.Headline !!%>" > </a> </li> </htmltext> </output> </foreach> </reddot:cms> Regards, Kent --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/RedDot-CMS-Users?hl=en -~----------~----~----~----~------~----~------~--~---
