Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
We're using user_relationships and have recently started to implement content sharing between associates. What I'm submitting is a patch to user_relationships_node_access.module that adds more controls to who can share and what nodes, and some usability improvements to make it simpler for plain jane users. The changes are:
- View, Edit, and Delete permissions can be granted separately to roles you choose: 'grant delete permission to related users', 'grant update permission to related users', 'grant view permission to related users', see the standard Drupal user permissions page.
- You can pick content types that may be shared. For example, we use content_profile to keep user profiles, so profile nodes should not really be shareable between one's associates. Settings are in Admin - Content Management - Posting to social network.
- If a user doesn't have all three permissions to grant view/edit/delete, they only see the allowed ones. If they have only one permission, the fieldset is reduced to a single checkbox 'Post to {relationship type}' instead of the table fieldset. This is to keep the UI simple if users are just sharing the view permission.
- Wording is different when organic groups are enabled to highlight that associates get access even if they aren't members of the groups.
No change in how access control works as the module is pretty great already. Any feedback or changes you see would be great.
Thanks!
Comment | File | Size | Author |
---|---|---|---|
usability_improv.patch | 7.69 KB | alex.k@drupal.org |
Comments
Comment #1
alex.k CreditAttribution: alex.k commentedCommitted to the 6.x branch.
Comment #2
Anonymous (not verified) CreditAttribution: Anonymous commentedAutomatically closed -- issue fixed for two weeks with no activity.