If the user has full node adminstrative rights, when cloning a node, the author field will be prepopulated with the previous author rather than be set to the new author. Not really a major problem, but an annoyance in that the author has to delete the previous author and enter their own username instead.

CommentFileSizeAuthor
#1 clone-name-5-2-166684-1.patch689 bytespwolanin

Comments

pwolanin’s picture

pwolanin commented
Version: 4.7.x-2.x-dev » 5.x-2.x-dev
Status: Active » Needs review
StatusFileSize
new clone-name-5-2-166684-1.patch689 bytes

this should not be happening, since the code makes the assignment: $node->uid = $user->uid;

However, I'm seeing this too with the 5.x version.

Here's a patch for the 5.x-2 branch - apparently $node->name needs to be set too. please test.

pancho’s picture

pancho
Location UTC+2 🇪🇺 EU
commented
Status: Needs review » Reviewed & tested by the community

Works.

pwolanin’s picture

pwolanin commented
Status: Reviewed & tested by the community » Fixed

patch committed to both 5.x branches and HEAD

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

  • Commit ffd45e1 on 6.x-1.x, 7.x-1.x, master, 8.x-1.x by pwolanin: 
    #166684 Author does not reset properly