[support] Controlling Node Access For Projects

[Earnie Boyd]

Quoting Steve Edwards <killshot91 at comcast.net>:

> I looked into it, and my customer had looked into it, too.  The one 
> problem they have is that with Content Access and
> Projects/Issues, the access you assign at the project level doesn't 
> filter down to the issues, so you have to go into each issue
> to assign access.  What I am trying to do is create a blanket 
> permissions access so that what is true at the project level is also
> true for issues.
>

Content Access [1] uses ACL [2] which is an API that content access 
uses so you should be able to extend it.

> That all being said, I go back to my original questions: will using 
> these hooks override what is in the Project module?
>

That is the way it is supposed to work, yes.

[1] http://drupal.org/project/content_access
[2] http://drupal.org/project/acl

Earnie -- http://for-my-kids.com/
-- http://give-me-an-offer.com/