Problem/Motivation

At the moment the admin page for Quick node clone at admin/config/quick-node-clone only seems to list custom fields which are allowed to be selected as excluded when a contenet is cloned.

We would like to also make sure that any cloned content would not carry any core field settings like Sticky at top of lists or Promoted to front page to be cloned.

Basically we have limited the user roles which can promote content to front page but it seems like it's possible to bypass this permission by cloning the content.

Steps to reproduce

1. Create a new content and mark it as Sticky at top of lists.
2. Clone it.
3. Make sure that the Sticky at top of lists setting was also cloned.

Proposed resolution

Add also the core fields to the list of possible excluded fields in the admin user interface and unset those fields from the form.

Remaining tasks

-

User interface changes

Add the excluded core fields to the admin user interface.

API changes

None.

Data model changes

None.

CommentFileSizeAuthor
#6 3358988-1.patch4.76 KBrishabjasrotia

Issue fork quick_node_clone-3358988

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

HeikkiY created an issue. See original summary.

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

TommiM opened merge request !15

tommim’s picture

tommim commented
Status: Active » Needs review

MR adds possibility to include / exclude Sticky at top of list and Promoted to front page fields from Quick Node Clone settings.
Gets default values from node bundle and if not selected in settings, uses them.

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

rishabjasrotia’s picture

rishabjasrotia commented
StatusFileSize
new 3358988-1.patch4.76 KB

Tested patch working fine in plain Drupal setup.

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

bluegeek9 changed the visibility of the branch 8.x-1.x to hidden.