I'm not sure that I agree it's best to leave content pages out of navigation manager. I wonder what other developers have to say about it?
The flooding of the nav - might you manage that with levels (don't display after level 3), and/or using a flag on each page to keep it from displaying in navigation? If you make the class in question a master class, do you see a significant slow down in Smart Edit or Publication? (after it caches the first time) How many pages do you anticipate having in your project? My opinion on target containers: They're an evil legacy ... mostly. Use with extreme caution. On Jul 12, 1:18 pm, damon <[email protected]> wrote: > Hi guys, > > I'm using Navigation Manager to create selected and non-selected > nodes. In doing this, I've discovered having non master pages in your > tree causes the navigation to lose it's "path" so to speak; I'm left > with my navigation set as non-selected for all nodes. > > Now, if I change the template to a master page it works fine. I've > been taught that it's best to leave content pages outside nav manager > for a few reasons, one being it'll flood my nav. manager with dozens, > and later hundreds and possibly thousands of pages in the future. > > Is there a way to retain the selected node states in my navigation on > my non-master content pages? Seems like I might have to do this > outside of navigation manager which would defeat its purpose. > > thanks > -Damon -- 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.
