This is how we do our 'children list':

<ul>
    <reddot:cms>
         <foreach itemname="SubIndex"
object="Context:CurrentIndex.SubIndexes" countername="counter">
             <if>
                    <query valuea="Store:counter" operator="=="
valueb="Int:0">
                        <htmltext><li class="first"></htmltext>
                    </query>
                    <query type="else">
                        <htmltext><li></htmltext>
                    </query>
              </if>
                <htmltext><a href="<%!! Store:SubIndex.GetUrl() !!
%>"></htmltext>
                <if>
                    <query
valuea="Store:SubIndex.Page.Elements.GetElement(stf_page_title).Value"
operator="==" valueb="Escape:Null">
                        <htmltext>This page needs a title!</htmltext>
                    </query>
                    <query type="else">
                         <htmltext><%!!
Store:SubIndex.Page.Elements.GetElement(stf_page_title).Value!!%></
htmltext>
                    </query>
              </if>
              <htmltext></a></li></htmltext>
        </foreach>
    </reddot:cms>
    </ul>

It puts a class on the first list item and grabs the placeholder of
stf_page_title if it has one, otherwise it gives a friendly reminder
to the user to fill the title in!

Anyway, hopefully this will be  of help too, I know what a pain NavMan
can be sometimes, I still haven't got my head around it!

On Jun 27, 11:43 am, thebiglife <[email protected]> wrote:
> Received an email reply highlighting that I could simply do this with
> a List referencing the main navigation List. I didn't think it would
> be that simple! Thank you Richard Hauer!
>
> So essentially my landing page now has a list_Children which
> references the main list_Navigation of the site. This list_Children
> displays the landing page's immediate children. Now, what if i needed
> to some clever stuff to the html of the list tag? add a css class to
> every other child li tag? I've come across one use of modulus in these
> threads using render tags, is this the best/only way?
>
> I'm asking quite a few questions on here as I'm a newbie. I've been on
> a few courses and picked up a weighty manual that covers the basics. I
> have access to the Knowledge base at OpenText, but I dont really seem
> to find much appropriate information. Where else should I be looking?
> I'm working/practising feverishly here, waiting for the penny to drop
> and it all make sense but I'd kill for some more advanced
> documentation.
>
> On Jun 26, 1:55 pm, 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to