Skip to content

[5.x]: Allow bulk publishing duplicated entries created as drafts #18954

@alexanderloewe

Description

@alexanderloewe

What happened?

Summary

When duplicating multiple entries in Craft CMS, the duplicated entries are created as drafts. This is understandable as a default behaviour, but it becomes cumbersome when the duplicated entries are intentionally meant to be reused and published exactly as they are.

Problem

If a user duplicates a larger number of entries, for example 20–30 entries, each duplicated draft currently has to be opened individually in order to publish it.

This creates unnecessary manual work, especially in content structures where entries are duplicated deliberately and only small changes, or sometimes no changes at all, are required afterwards.

Expected behaviour

It would be helpful if duplicated draft entries could be published via a bulk action.

For example:

  1. Duplicate multiple entries.
  2. Select the duplicated draft entries in the entry index.
  3. Use a bulk action to publish them or set them to enabled.
  4. The selected drafts become regular published entries without having to open each one individually.

Possible solutions

One of the following options would already solve the issue:

  • Allow the existing bulk status action to publish selected draft entries when setting them to Enabled.
  • Add a dedicated bulk action such as Publish drafts.
  • Add a dedicated bulk action such as Convert drafts to published entries.

Why this would help

This would make larger duplication workflows much faster and cleaner, especially for navigation entries, repeated content structures, landing pages, or similar content setups where entries are intentionally duplicated and then reused.

At the moment, the workflow is technically possible, but unnecessarily repetitive for larger batches.

Craft CMS version

5.10

PHP version

No response

Operating system and version

No response

Database type and version

No response

Image driver and version

No response

Installed plugins and versions

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions