My setup is like this:<br><br>I have two CCK types, project and task.<br><br>Then under admin/settings/og<br><br>Have the following selected:<br><br>- New groups don't appear in the groups directory. Administrators control the directory exclusively.
<br>- New groups don't appear in on the registration form. Administrators control the form exclusively.<br>- Audience checkboxes (unchecked) <br>- Audience required (set to required)<br>- Presentation style : Group by content type
<br>- Group home page node types: group only<br><br>This way, the groups are invisible, and people have to be added explicitly to a group<br>and hence the other groups are invisible to a given person who has access to group A,
<br>but nothing else.<br><br>When a user creates a task, the audience is already there (group name).<br><br><div><span class="gmail_quote">On 1/2/07, <b class="gmail_sendername">Boris Mann</b> <<a href="mailto:boris@bryght.com">
boris@bryght.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On 1/2/07, Khalid B <<a href="mailto:kb@2bits.com">
kb@2bits.com</a>> wrote:<br>> I am also playing with casetracker, CCK (for node types), and og (for<br>> separating<br>> each project/client).<br>><br>> So far it is promising for sure, but can't give it more time in the upcoming
<br>> weeks.<br><br>So....I looked at this (casetracker + OG), and there seem to be some<br>problems unless I am missing something. Let me walk through the recipe<br>and where I ran into issues (from memory, and the site is since
<br>reconfigured):<br>* set OG settings to OG-enable project nodes (casetracker_basic or<br>whatever it's called)<br>* control cases (+ pages, stories, image, etc. etc. as needed) with OG<br>* create project == creating a group (no problem)
<br>* subscribe users as needed to the group<br><br>Problem: associating a case with a project doesn't protect it -- you<br>need to select the project AND the "audience", which is a duplicate of<br>the projects (just the OG access control).
<br><br>Problem (same with all OG, of course): need to manually subscribe all<br>people that need access to each project.<br><br>Ideally, OG enabled project nodes would have cases automagically<br>access controlled with the parent projects OG...blah...that was as
<br>hard to say as it is to do.<br><br>I ended up implementing this with tac_lite and casetracker: both cases<br>and projects are assigned to role access categories, and it seems<br>simpler. When creating new projects or cases, visibility is tied to
<br>one category which gives access to everyone that needs it in one fell<br>swoop. Also, you can have "more private" cases (e.g. your dev team can<br>post stuff in a customer project without exposing it) easier.
<br><br>And, of course, there is email notification from both casetracker and OG.<br><br>Hope that provides some interesting feedback,<br><br>--<br>Boris Mann<br>Vancouver 778-896-2747<br>San Francisco 415-367-3595<br>Skype borismann
<br><a href="http://www.bryght.com">http://www.bryght.com</a><br>_______________________________________________<br>consulting mailing list<br><a href="mailto:consulting@drupal.org">consulting@drupal.org</a><br><a href="http://lists.drupal.org/mailman/listinfo/consulting">
http://lists.drupal.org/mailman/listinfo/consulting</a><br></blockquote></div><br>