This set of render tags will get you child pages from a parent, or from within a page in a container on the parent. I think all the syntax is correct - hopefully didn't introduce any errors when I made them generic. You can use them anywhere in the tree, since they just target the children of the current page, and you won't need to use list to reference another list. It's getting the headline, but you could use .Elements.GetElement (stf_SomeElement).GetHtml() instead of .Headline In this way, your navigation will match the nav index, not the list order. this might be beneficial if you are using nav manager.
<reddot:cms> <htmltext><ul></htmltext> <foreach itemname="pageIndex" object="Context:Indexes.GetIndexByPage (Context:CurrentMasterPage).SubIndexes" countername="pcounter"> <htmltext> <li> <a class="current" href="<%!! Store:pageIndex.Page.GetUrl() !!%>"><%!! Store:pageIndex.Page.Headline !!%></a> </li> </htmltext> </foreach> <htmltext> </ul> </htmltext> </reddot:cms> This will get you the same thing, but from one of the child pages, showing its siblings (it reaches back up to the parent, then down to children in case you wanted the component on specific pages) <reddot:cms> <htmltext><ul></htmltext> <foreach itemname="pageIndex" object="Context:Indexes.GetIndexByPage (Context:CurrentMasterPage).Parent.SubIndexes" countername="pcounter"> <htmltext> <li><a class="current" href="<%!! Store:pageIndex.Page.GetUrl() !! %>"> <%!! Store:pageIndex.Page.Headline !!%></a> </li> </htmltext> </foreach> <htmltext> </ul> </htmltext> </reddot:cms> Can't think off the top of my head how you would do something for every other row. Maybe there's a modulus function you could use with: <if><query valuea="Store:pcounter.MODULUS(0)" operator="==" valueb="Int:0"> Lastly, this is some code I wrote mixing render tags with a list. It goes through the list, and then gets info from components (pages) within a container on the page connected to the list. <!IoRangeList> <li> <a href="<%list_Children%>" class="someClass"> <img src="<%!! Context:Pages.GetPage(Guid:<%info_PageGuid %>).Elements.GetElement(con_PageLayouts).Value[Int: 0].Elements.GetElement(img_SomeImage).GetHtml()!!%>" /> </a> <h4><%!! Context:Pages.GetPage(Guid:<%info_PageGuid %>).Elements.GetElement(con_PageLayouts).Value[Int: 0].Elements.GetElement(stf_Title).GetHtml()!!%> </h4> <%!! Context:Pages.GetPage(Guid:<%info_PageGuid%>).Elements.GetElement (con_PageLayouts).Value[Int:0].Elements.GetElement (txt_SomeText).GetHtml()!!%> </li> <!/IoRangeList> Hope they help or at least give you some ideas. Wayne. On Jun 26, 6:55 am, thebiglife <[email protected]> wrote: > Hello, I'm on about day 10 of learning Red Dot CMS, it's getting > easier thanks to posting questions here and getting good answers. But > here's another question, potentially Navigation Manager related. > > I have all the basic NavMan components working, sitemap, breadcrumbs > etc... but I have one more requirement which may be something I can > get out the NavMan. We have a 'Landing Page', a basic page that > displays a listing of its immediate child pages (just one level deep). > Is this achievable with NavMan and rendertags? > > I thought I could use <%!! Context:CurrentIndex.HasChildren() !!%> but > this seems to give me the root page of the site, rather than the > actual current page? > > Another stipulation here is that I'll need to use the landing page > content class in several places, so the iteration of the children > needs to be generic. (i.e mentionning this because this > ideahttp://groups.google.com/group/RedDot-CMS-Users/browse_thread/thread/..., > doesnt seem to allow that level of flexibility) > > So how would you guys do it? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
