- Issue created by @mmafe
We have a website that restricts edit access for nodes using Workbench Access. All users on the website can view content from other Workbench Access groups, but they cannot edit that content unless they are part of the correct Workbench Access group.
As part of their workflow, many users often clone each other's content and rely on the Quick Node Clone module and its Clone operation to do this.
After upgrading to version 1.21, we noticed that users can now only clone nodes that they can access through their Workbench access permissions (see https://www.drupal.org/node/3398866 → ).
I can see how some groups using Workbench Access would want to limit clone access based on node access. However for our users, they still prefer the idea of being able to clone content outside of their particular group.
1. Install Workbench Access (
https://www.drupal.org/project/workbench_access →
)
2. Create a taxonomy-based access scheme with at least two groups, Access Group A and Access Group B
3. Create a content type with a field that restricts node access based on the access scheme
4. Create a node of the access-restricted content type and set the access so the node is restricted to Access Group A
5. Create a second node of the access-restricted content type and set the access so the node is restricted to Access Group B
5. Add a user to Access Group A
6. When viewing all Drupal content, you'll notice the user only has access to clone nodes that they can access via Access Group A. However they do not have access to clone nodes that are associated with Access Group B.
Is there any way to make it so users can still have the ability to clone content (similar to how it was prior to the recent update), even if they do not have access to edit that content? (Note: I would prefer not to give users additional permissions such as Bypass Node Access if we can avoid it.)
Thank you for looking into the question!
Active
1.21
Code