This is along the lines of my last thread re: Site tree root node. What are people doing to separate content objects among organizational groups, depts, etc?
For instance, say you have a custom type that you want to deploy to all of your users, but you only want each group of users to see their OWN content listed both on their pages within the site AND the admin interface. Sure, you could use the category tree, but then you have to trust that the user creating the content chooses the right category (their own). What I've done is store an array of the user's policy group ID's with each content object, and then I only list ones that match on the admin side. Also, my rules have a policy group IDs property, which allows the user defining the rule to specify which content to output (which means later, if needed, I can easily combine multiple group content, etc) Is there a better way to do this? It seems to work pretty good... any pitfalls associated with this approach? What do you guys do in this type of situation? thanks, Dave --- 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
