Looking for advice... client wants different groups sandboxed to their own section of the site (in site admin). They DON'T want the users to see any other section of the site (even though the permission settings won't allow edits in sections other than their own). I can hack the core index.cfm and set url.rootobjectID eq to the highest level node that they have appropriate permissions for, but ideally I'd want to have a policy Group field that holds a nav alias, identifying the default root node for the tree when users of that group log in. Is there any other desire for this functionality out there? (I saw a thread or two in the archives) The changes are not huge... pros/cons? I know one con is that once this default root is set, users of that group will not be able to modify sections of the site, at or above that level... but I can accept that.
thanks, Dave Ross --- 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
