it is very simple and good module,
Is there any possibility of integrating with rules, like on certain conditions "grant permission to view/update/delete" and "remove permission" to view/update/delete content?

Comments

Dave Cohen’s picture

Dave Cohen CreditAttribution: Dave Cohen commented
Issue tags: +get involved

You mean a rule to give/revoke a specific user a specific privilege?

I suppose that is possible. I know little about the rules API. If someone wants to contribute a tac_lite - rules integration module, that would be cool. Could be stand-alone or I would put it into tac_lite/contrib.

kaizerking’s picture

kaizerking CreditAttribution: kaizerking commented

yes, exactly,content access has got the same function along with ACL, but it works for general content,not specifically for terms. may be some of the code/ideas can be picked from there.it may be a good idea to support Content access as both or node access systems and can work hand in hand but TAC lite should be working independently,as content access will be heavy for smaller sites. I am not a coder so cant help on code.
ACL is the API for content access "Access Control Lists, is an API for other modules to create lists of users and give them access to nodes. It has no UI of its own and will not do anything by itself;"

Dave Cohen’s picture

Dave Cohen CreditAttribution: Dave Cohen commented

I can imagine a rule that gives a user access to a tac_lite scheme. But, tac_lite will always be about terms and access to the nodes tagged with those terms. There are lots of access control modules that use other criteria.

kaizerking’s picture

kaizerking CreditAttribution: kaizerking commented

Yes, there are many for node access with other criteria,access to the nodes by term,there are very few, and those which are available , have entity support issues.like Term access and ABT .What I have noticed is an entity based term access approach is much needed.which will facilitate an easy link to rules.i think it is time to clear the lobbies for entities like profile2, many developers are still stuck with core profile.and are not planing for a migration path.TAC lite rules integration will be a rescuer for this issues
I think it is worth keeping in mind the taxonomy hierarchical select while planning the rules integration,
1.We have multiple terms,
2.Hierarchical select allows to save the deepest term and also allow multiple terms
I have put this to list out challenges for the TAC lite rules integration
I am not sure if a term is treated as an entity, if it were then the job would be easier
EDIT:
while I was trying to set rules to do a data comparison i got this idea on conditions
1.entity has a term(a.equal to b.one of- for multiple value)
2.node has a term(a.equal to b.one of -for multiple value)

Permissions
1 grant permission(a.view b.update.c.delete)
2.revoke permission(a.view b.update c.delete)
Further search in rules issue que in rules i found that already it is under discussion better to have a follow up with that issueCondition: content has term it is a fresh issue and a patch has been submitted for review, if this also can be taken up with that it will save a lot of time and efforts

Elin Yordanov’s picture

Elin Yordanov CreditAttribution: Elin Yordanov commented

Bump!

tinker’s picture

tinker CreditAttribution: tinker commented

As a start I just posted functions to grant and revoke user access. These are for 6.x but should work on 7.x with little or no modification. These could be used as action in rules. #2028217: Grant & Revoke functions so other modules can use TAC lite

tinker’s picture

tinker CreditAttribution: tinker commented

Doh! TACle Rules
Not for D7 but that would probably be a better place to request a D7 version.

tinker’s picture

tinker CreditAttribution: tinker commented
Assigned: Unassigned » tinker
Status: Active » Closed (fixed)

Took over as maintainer of TACLe rules. Posted 6.x-2.0-alpha1 a few days ago which is a complete rewrite of the module. Just posted 7.x-1.x-alpha1 release which is a port of 6.x-2.0-alpha1. Both have actions to grant/revoke term access to single user account and roles. Can be used with single term or multiple terms. Conditions to check term is controlled by TAC and if user has access to terms (by individual term or by role).

I suggest moving future Rules discussion to TACLe Rules module.