[farcry-dev] Re: Unnecesary Left Nav Expansion for News Content Type via rule.

[Blair McKenzie]

I can't remember off hand whether news items can be added directly to the tree, which would solve this problem automatically. If they can't by default, you can change them so they can by extending dmNews and including bUseInTree="true" as an attribute of custom type. Once news items can be put directly onto the site tree, simply make sure that users do it that way instead of through the content tab.

Blair

On 10/7/06, Chris Roth <[EMAIL PROTECTED]> wrote:

Blair,

thats sounds like it will work, but only one problem...

In the site, I have multiple divisions that have thier own press
release (news) sections that are populated with the news rule
restricted by category. if I hard code
navID=#application.navid.presssrelease# for ther genericNav for my news
page, it will only be correct (usability wise) for users viewing the
"main" press releases, but not for example Division1>News &
Events>Press Releases> Some release

Is there any other variable I can set to make the nav sticky to the
current nav node I am in?

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "farcry-dev" group.
To post to this group, send email to farcry-dev@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/farcry-dev
-~----------~----~----~----~------~----~------~--~---