Giving user permissions to clone both own node and node results in no clone rights [#1369986]

I'm a newbie - so I might miss something

Installed node clone on Drupal commons

Then gave authenticated users to both clone own node and general node.
The authenticated users could not clone.
First thought that the issue was I'd givne rights to both clone own nodes and general nodes, but the effect was the same.

Could only get it working for content managers, not authenticated users.

Comments

Comment #1

pwolanin CreditAttribution: pwolanin commented 1 January 2012 at 20:46

Status:

Active

» Postponed (maintainer needs more info)

please provide more detailed steps to reproduce. Quite possible this is due to the user not being able to access the input format for the node body.

Comment #2

ChrisValentine CreditAttribution: ChrisValentine commented 5 April 2012 at 11:02

I have exactly this issue - the clone tab simply does not appear for some records for users "lower" than Admin, even though they are permitted to create new records of the same node type; clone works fine for the Admin user for all records of that node type.

Its not simply due to the presence of CCK fields in the node definition - it appears more to be related to who created the "source" node. Is it possible that nodes created before the Clone node module was installed are not cloneable?

Comment #3

websitetechnician CreditAttribution: websitetechnician commented 13 April 2012 at 21:24

Are you by chance trying to clone nodes that are currently unpublished with users who do not have the "administer nodes" permission? I ran into that situation earlier. Users could clone their own unpublished nodes, but couldn't clone others unpublished nodes if that user didn't have "administer nodes."

Comment #4

ChrisValentine CreditAttribution: ChrisValentine commented 17 April 2012 at 13:36

> Are you by chance trying to clone nodes that are currently unpublished...?

Have just checked that but no, these are some published nodes.

Comment #4.0

ChrisValentine CreditAttribution: ChrisValentine commented 17 April 2012 at 13:36

Issue summary:

View changes

Updated - better qualified the issue - related to the authenticated user, not to content manager

Comment #5

sterlingedsrv@gmail.com CreditAttribution: sterlingedsrv@gmail.com commented 20 November 2013 at 21:29

Did this get resolved? I seem to be having the same issue.
I have a user, Bob, that can add and edit a specific node type regardless of the original author, but they are not an admin.
Today I installed the node clone module and gave Bob both permissions for it.

Two problems:

Major - Once cloned, there are 4 fields that it says Bob can't edit on the cloned node. It says "This field has been disabled because you do not have sufficient permissions to edit it."
What other permissions does Bob need??

Minor - Bob is able to click "clone node" from a node page, but not from the content list (which I can as an admin)