The menu tag also uses request.sectionObjectID to check for the active node. Of course, if you end up putting the jobs on the tree itself, you won't need all this stuffing around with the menu.

Now that the type has the bUseInTree attribute, you should be able to add it to a node by right clicking the node -> Create... -> NameofType.

As for a rule, there is no rule that displays all of a given type that are children (though some have some of that functionality). ruleChildLinks does what you want for html pages, so you can use a copy of that to create your own rule with a minimum of effort.

On 8/12/06, Chris Roth <[EMAIL PROTECTED]> wrote:

Andrew, thanks for the heads up on bUseInTree="1"

this is interesting. and it achieved the navigation effect i was
looking for. however, this poses some additional questions for me that
I hope you can answer.

1. lets say I have created 5 jobs using the content method, is there a
way to now put them in the tree?

2. is there some out of the box rule, or other method to generate the
list of jobs that are in the tree on the parent page?

meaning, if I have the careers (nav) - > curent openings (nav) >  Job
list (html) > job1 (job) job 2 (job) in the nav structure, and I use
the insert in to tree type method of entering the jobs, how do I
dynamically display the list of jobs on the Job List (html) object?

... ok answered this one my self, I can use the jobs rule I created for
diplaying the job list when i made my custom type..

except, I still have the issue of setting the "active" node in the nav
so its highlighted.

still looking for answer to this (my reply to blair earlier today) and
#1 above.

THANKS!

Chris






--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "farcry-dev" 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/farcry-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to