Rules integration

yep, that's the plan. Try the recent development snapshot of content access. I plan to add also per user support there on top of the ACL integration.

@fago: Rules integration pretty much amounts to coding actions, right? Another possible route is to use #329500: support for looping and data lists and nodeaccess_userreference.

My use case scenario is to let users pick who they want to have view, edit, delete privileges (nodeaccess_userreference does this well), and also have actions to automatically give and take away those privileges from users(s) using rules.

yep, this would be fine for building an own frontend for the ACL integration.

I've just added 2 new actions to the module: For granting or revoking per user access permissions.

Automatically closed -- issue fixed for two weeks with no activity.

Where would one need to create rules to mimic nodeaccess_userreference etc for use in rules? Does this exist already? I couldn't see anything. Or does it just not matter, and I should use that module^ ?

Edit: that module seems to work fine, but it seems like finer-grained, UI based control could easily be achieved to replace it, and its counterparts.

Hi,

The rules implementation is working great. But I noticed that when triggering a revoke or grant access in rules, eg, Revoke content permissions by role, it revokes the permission for all your own nodes, is there a way to trigger on per node?

Thanks!

I've a content type (call it: X) with two fields:

- node reference (to another content type, Y)
- user reference

when I update an X node, I'd like to set the referenced node view permission to the referenced user.

I've created a simple rule:

The first time the argument of the action are setted, they displays the to cck fields. But, when the rule is saved, them are deleted (so you have to manually load the fields).

I don't know if it is a rule problem or a content_access + ACL issue.