Closed (fixed)
Project:
Drupal.org CVS applications
Component:
new project application
Priority:
Normal
Category:
Task
Assigned:
Issue tags:
Reporter:
Created:
13 May 2010 at 10:22 UTC
Updated:
30 Dec 2018 at 09:05 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
splash112 commentedModule attached
Comment #2
avpadernoHello, and thanks for applying for a CVS account. I am adding the review tags, and some volunteers will review your code, pointing out what needs to be changed.
As per http://drupal.org/cvs-application/requirements, the motivation message should be expanded to contain more details about the features of the proposed module, and it should include also a comparison with the existing solutions.
Comment #3
splash112 commentedThanks
As far as I know, there is no similar module yet.
This module maintains a simple uid, tid table linking uid's to term's in a User as Term vocabulary.
Reason for doing so is utilizing the powerful Taxonomy system in Drupal for organizing users, especially useful for companies. We can now do:
the boss
- manager 1
- manager 2
- - Employee 1
- - Employee 2
- - - Assistant 1
I want to use this for a project site and write and additional ACL module that delegates rights upwards. If assistant 1 has the right to edit a node (because of a user reference, or just as owner), employee 2 will automatically get it too, and maybe even manager 2 or the boss, while employee 1 and manager 1 don't.
Comment #4
avpadernoThanks for the explanation.
Comment #5
splash112 commentedUpgraded the proposed module, it's more refined now.
Also included 2 functions which will return either all parents from a user (uid and term info) or related (uid and term info).
Hope somebody want to have a look.
Comment #6
splash112 commentedAnd another version.
Now included is a ACL module which is a first step to get the the true power of using the taxonomy system for users.
Userreference rights to nodes are also given to the "parents" of the user and to "related", just like in a Taxonomy.
Still; need to figure out how to mass update the ACL rights after changes are made in the Taxonomy tree. Probably have to re-save all nodes again, possibly easiest done by a Views Bulk Operation.
Hope somebody would have a look.
Comment #7
splash112 commentedNew version which does not get comments from coder.
Comment #8
nikhiljha commentedHi spalash112,
I have similar requirement for one of the NGO I am working for. I was browsing through source code. and I want to know if "acl_hierarchical_perms_userreference" is not set (no user reference field) will the acl_hierarchical_perms.module work? And if we are not using nodereference field where we are are setting "acl_hierarchical_perms_userreference".
Thanks
Nikhil
Comment #9
splash112 commentedHi Nikhil,
The modules are still very much an idea, far from a perfect/stable solution. So be extremely careful on when you use it.
Basically it makes an ACL for every node and and every user. Via a vocabulary_get_parents, it assigns that ACL to the user (which is strangely an output of vocabulary_get_parents) and all it's parents. So in you case, the acl would be assigned to only the user.
It seems to work for, more or less, static vocabulary trees. If you change the tree significantly, you would probably do an update on all nodes before changes take effect in all nodes. So that part need some work still.
Comment #10
zeezhao commentedSounds interesting. Has there been any further development on this?
Right now, I have a Taxonomy for Business Units which is hierarchical. Will be nice if both can be linked together. Do you already do somthing similar?
Comment #11
avpadernot()is available whenhook_install(), orhook_uninstall()are invoked. See the code executed from<a href="http://api.drupal.org/api/function/php_install/6">php_install()</a>as example.Comments for other functions should be like the following one:
Descriptions should be sentences ending with a period.
Comment #14
avpadernoComment #15
avpaderno