As the note says in the project page, 2.x will be a different thing than 1.x. Initially 1.x developed because there were no Content Access for D7 back then, now Content Access has a working D7 release. I'm opening this issue to discuss the features, please if you have a good one be bold and add it :)
My wanted feature:
- Support user reference field, so for example if you have 3 user fields inside a node, the first one will be granted edit, the second user will be granted deleted and the third view only, of course this is an example you can swap/play with the operations (view, edit, delete) as you want with as many users as you want. The definition for this little ACL will be set from admin page.
Comments
Comment #1
ckngI'm thinking something like user group, without the complexity or features of OG.
On top of selecting individual user, an UI to create user group (without abusing role) to contain predefined list of users, then on the access page to select these group(s), cutting down a lot of repetitive job.
e.g. users could be from the role student, but could be assigned to group classA, paperB, yearC, etc. to access different content.
I'm not aware of group access control like this exist in Drupal.
What do you think?
Comment #2
JohnnyX commentedI would love it! User should create own friend lists/ groups and add/ remove users to it. Based on these groups the user (himself) can grant other users view/ edit permissions to own nodes!
Any change to get it?
Comment #3
gisleI think the user group idea (suggested by ckng above) is great.
However, as an interim solution (as this is easier to implement) I suggest that there is at least one default user group containing everyone (i.e. all authenticated users). The current Flexi Access is great when one, as an exception, wants to add a single user to a the access list for a node. However, if you want to exclude a few users, but grant the majority access, you must create an ACL by adding a lot of users one by one. Having a quick way to populate the ACL with everyone, and then just ticking boxes to remove the few persons that are excluded would be a time saver.
I also want to have a way to remove the ACL from a node, restoring access to all. (It may be that this is the intended purpose of the "Reset to default"-button, but this is not what it does now. I don't think I understand what this is supposed to do.)
Comment #4
ckngI probably should update this thread. I've opted for Simple Access instead, more info at #1397074: Support per user and user group.
The related module: http://drupal.org/sandbox/ckng/1398430
Comment #5
gisleI have taken over as new maintainer of the module.
My first priority has been to fix the bugs in the present code and to make sure the source code conforms to Drupal coding standards. I hope that this has been accomplished with the development snapshot I uploaded today.
As maintainer, I've dropped the idea of a version 2.x of the module. Instead, I want to pursue the idea of making the Flexi Access module into a flexible user interface for ACLs (Access Control List) module. I am still interested in ideas for features to add, but I want to keep the module focused on handling ACLs.
Comment #6
ilsa commentedI think group control is well beyond the scope of this module. Personally, and especially initially, it shouldn't go beyond handling individual users, and roles.
If at some point you want to provide support for other group mechanisms (eg: Organic Groups) than that's always nice, but I agree that this module should do one thing well: Handling node ACLs. I am absolutely shocked that such a module hadn't been created a long time ago (and by created, I mean actually make it out of beta status).
Someone else mentioned Simple Access. And while interesting, it is yet another module that appears to have been abandoned before it even reached a final release and hasn't been updated for over a year and a half.
Thank you very much for your efforts!
Comment #7
gisleThe Drupal 7 port of Flexi Access is done.
If there are any new bugs reports (or feature requests), please create a new issue.