Posted by bonobo on October 22, 2008 at 8:08pm
4 followers
| Project: | Node access user reference |
| Version: | 6.x-1.0 |
| Component: | Miscellaneous |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
See http://drupal.org/project/userreference_access and http://drupal.org/project/coherent_access
These three modules should probably get rolled into one.
Do you want to centralize discussion on this issue: #323890: Userreference_access -- working together?
Comments
#1
@bonobo: This is by far, the best effort to provide a node access form element. Thank you danielb, and I must say, great timing.
Userreference Access: My aim with this module was to accomplish exactly what nodeaccess_userreference does. It's now not worth the effort to fix and then port to it to 6.x. This module does exactly what I was hoping for, but it still needs grant 'edit access'.
Coherent Access: it has the right features, but uses it's own form element instead of userreference and is not as configurable as this method.
Content Access & ACL: I can't remember what these have and don't have. I'm going to take another look at it later and see if it is integrated with Rules. If so, I think it'd be useful in other ways along side this module.
#2
it would take me a minute to add in edit/delete access
sorry guys had no idea about those other modules.
#3
I added the edit/delete access in 1.1 but I have not used it
#4
@danielb -- no worries --
One of our roadmap items for coherent_access in D6 is replacing the existing form elements with CCK user reference fields -- we'll be going down that road ourselves in any case, as we have been using coherent_access for a variety of purposes across different sites. We'd welcome collaboration around coherent_access; it would reduce duplication of effort, result in better code, and result in clearer options for users. It would also reduce all of our maintenance burdens over time; multiple maintainers around one module can do more work than multiple maintainers fragmenting time across several similar modules.
#5
It just doesn't seem to me like coherent access is similar enough to this module. You say you want to make it more similar to this module, but the fact is that it currently does not do what I need it to do, and there is no information about plans to go down that road, and that is to give node access to someone entered in a user reference field. It seems coherent access does not need to depend on CCK at all, has a messaging system, and such features that could take it down a different path.
And of course the biggest thing that bothers me is the name 'coherent access' which probably goes a long way to explain why I never found it. :/
#6
Yeah, I can't claim a great deal of pride re the name.
See the attached screenshot to see what I'm thinking re using user_reference fields in coherent access. The CCK dependency isn't a big deal from our perspective, as we really haven't rolled a site without it for a while anyways.
While I need to test your module and other new module referenced in this thread more thoroughly, I suspect we have comparable functionality lurking underneath dissimilar UI's
#7
Since the functionality revolves around a user reference field I would rather base such a project around this module. I've gone over the code too, and I think it would be easier to move the 3 or 4 extra options over to nodeaccess_userreference than it would be to rewrite the approach of using your own configs, storage, fields, etc... to piggybacking off the cck field, and the name makes more sense. I've done the email stuff in another node access module to notify the user, I kept the email templates with the others in user settings.
#8
Hello,
I've just tested your excelent module (I did something simular with only fixed content type and userreference field), but when I try your module, give view access to the userreference field, it seems not to work. The user doesn't get view access. Is it possible that I have to change the priority due conflicts with acl / content access?
Maybe I should open a new issue, don't know.
Edit: sorry it gives access to the referenced user, but not to translated nodes.
My setup: drupal 6.6, cck, i18n
I have a project node with clients (userreference field, role client, no default view grants), staff (another userreference field, but staff role has always view, edit access), the referenced staff has the projects on their account page, but other staff may view, edit them as well. Project node can be translated, synchronization of most fields, project_code, userreference fields, ... Only the language neutral projects will be shown on the user account page and have access rights.
HTH,
Fossie
#9