I decided to extend dmNavigation today and added the following properties: topnavVisibility (boolean) bottomnavVisibility (boolean) sitemapVisibility (boolean) permissionBasedVisibility (boolean)
Essentially they are to control how the nodes are displayed depending on which navigation bar is being displayed.
There must be a better way to do this? Although changing core types is possible, it shouldn't really be done except if there is no other way. The reason for this is maintainability. Every change you make to core by extension means you expose yourself to having to make additional changes when the core is upgraded.
Have you tried building auxillary menus in the Utility tab? Using symlinks to link to the same content from multiple locations?
Once I uploaded and deployed this extension the option to create a new nav node from the tree and from the overview pane has disappeared. I have no idea why or how to get it back. Can anyone shed some light on this?
It may be that the tree Javascript is behaving badly due to the additional data being provided in dmNavigation. If so, I'd suggest that's a bug but I'll Paul or someone more familiar with the JS library respond on that.
-- geoff http://www.daemon.com.au/
--- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
