#31198 closed feature request (maybelater)
Adding duplicate/clone to quick edit post screen.
| Reported by: | paaljoachim | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Quick/Bulk Edit | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description
Hi
What about adding a duplicate or clone option to the quick edit post screen? It would just be a minor addon but one that could really help when one needs to create multiple similar or identical posts/pages.
Similar to this plugin: https://wordpress.org/plugins/duplicate-post/
Change History (16)
#3
follow-up:
↓ 4
@
12 years ago
Almost 900.000 users have downloaded the plugin which signals that a lot of people need a duplicate/clone feature.
- It should be very little effort to add to core.
- Only visible on quick edit.
- Very useful when a person needs it.
It should be considered for core.
#4
in reply to: ↑ 3
@
12 years ago
Replying to paaljoachim:
Almost 900.000 users have downloaded the plugin which signals that a lot of people need a duplicate/clone feature.
- It should be very little effort to add to core.
- Only visible on quick edit.
- Very useful when a person needs it.
It should be considered for core.
Could you perhaps add a reasoning as to why this is plugin territory?
#5
@
12 years ago
This firmly feels like plugin material for now to me.
Although it's useful to a lot of people, it's potentially not useful for a large majority of the WordPress users out there.
For example, a plugin with 900k downloads probably only has 50% of those still as actual installs, so lets go conservative and say 600k active installs of the plugin, if you assume the 60million WordPress sites are split 50/50 between WordPress.com (which has a similar feature) and WordPress.org, that's about 2% of WordPress.org sites having the plugin active, and then there's how many posts are published using the copy-post feature vs writing a new post..
So that's my reasoning, a plugin that is used by a small percentage of users is probably best left as a plugin. Those who need the functionality can still get it, and those who don't need it, don't need the extra UI.
#6
@
12 years ago
Thank you for the reasoning @dd32.
Today there seems like three options on how to add features to a site. Through Core, a plugin or as a child theme functions snippet. It would be great to have a snippet library of features that are very useful for folks but that for their own reasons do not make it into core.
Have a great day!
#7
@
12 years ago
- Milestone Awaiting Review
- Resolution → maybelater
- Status new → closed
a plugin or as a child theme functions snippet
If the functionality is theme-specific, it should go in the themes functions.php, otherwise a plugin is the correct route for pretty much all non-theme alterations.
Resolving as maybelater for now, if in the future we decide it's worth core inclusion, we can revisit.
This ticket was mentioned in Slack in #core by paaljoachim. View the logs.
7 years ago
This ticket was mentioned in Slack in #core by clorith. View the logs.
6 years ago
#16
@
4 months ago
I think we should reconsider this in 2026. Any content management UX will have duplicate as a shortcut for complex copy n steps paste workflows.
My current thinking is that we should duplicate the entire content and its taxonomy and offer a way to replace the duplicate function per post type, so when post types are registered a duplicate callback can be registered as well. The basic post and page types should allow separate overriding of the default duplicate action.
So everything by default with override options.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
I'd say this is plugin territory. As you have suggested There is already a well used and well rated plugin that does exactly that for those who need it.