Problem/Motivation

In order to give a role permissions to clone all content types, every checkbox has to be checked. Then when a new content type is added, you need to remember to allow a role to be able to clone that content.

We have a use case where the 'Client Admin' role should always be able to clone content of any type.

Proposed resolution

Provide a new role 'clone all content'

Thanks!

Issue fork quick_node_clone-3508030

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

lindsay.wils created an issue. See original summary.

bluegeek9 made their first commit to this issue’s fork.

bluegeek9 opened merge request !50

bluegeek9’s picture

bluegeek9 commented
Status: Active » Needs review

I added a permission 'clone _any content'. There is no equivalent 'create any content' permission. I want feedback from the community before completing the MR.

lindsay.wils’s picture

lindsay.wils commented

Thanks @bluegeek9.

True that there isnt a 'create any content' permission, but we do have:

Bypass content access control
Warning: Give to trusted roles only; this permission has security implications. View, edit and delete all content regardless of permission restrictions.

So in the case you have a client managed website where they just have full access to create/delete/edit any content of any type, including new content types that may be created in future, you can assign this role.

It seems to me like a valid use case to be able to give a role the option to just clone anything, without worry.

Thanks