Per-content-type permissions [#421254]

Hi,
Thanks for this module, it does (almost) everything I need.
Here is a small patch to permit or deny roles to clone nodes on a per-content-type basis - that is, you can allow members of a role to clone one or more content types but not all.
The change is simple, and should be backwards compatible.

Comment	File	Size	Author
#3	node-clone-per-content-type-perms.patch	2.48 KB	james.cartledge
	per-content-type-perms.patch	1.15 KB	james.cartledge

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

pwolanin CreditAttribution: pwolanin commented 2 April 2009 at 19:28

hmm, while this makes sense - will also lead to a proliferation of permissions on the permissions page - guess that's ok, if ugly.

Comment #2

james.cartledge CreditAttribution: james.cartledge commented 2 April 2009 at 22:59

pwolanin - that's true. For my use case this functionality is needed, so I just have to live with that.
Would it be preferable if there was a setting for this, defaulting to the current configuration, or is that too much noise on the settings screen?

Comment #3

james.cartledge CreditAttribution: james.cartledge commented 2 April 2009 at 23:44

File	Size
node-clone-per-content-type-perms.patch	2.48 KB

Not sure if this is better - I've added a checkbox in the settings screen to make the change optional.

Comment #4

csc4 CreditAttribution: csc4 commented 6 September 2009 at 15:05

I'd like something similar to this, I don't want to let users edit a node of a particular type, but I do want to let them clone them and I think I'd need this patch to be able to do that?

Comment #5

pwolanin CreditAttribution: pwolanin commented 7 September 2009 at 20:34

@csc4 - right now clone is a global permission, so users can essentially clone any node if they can view it and they can create a node of that type with that format. This would lock things down more - though it's mostly a usability/workflow question I think, since users could still manually copy/paste content to create content like existing content.

Comment #6

csc4 CreditAttribution: csc4 commented 9 September 2009 at 18:01

Thanks for the clarification - I hadn't realised that the clone was only

if they can view it _and_ they can create a node of that type with that format

seems obvious now you say it! and that does help a bit.

I do still like the idea of tying the workflow - but perhaps that's the key, maybe this should be in workflow rather than the base module, then those wanting the simple case can keep it and we inveterate complicators can complcate things.

Clone is hugely superior to cut and paste - one of my core modules I always install! - thanks for your work on it.