#31198 closed feature request (maybelater)
Adding duplicate/clone to quick edit post screen.
Reported by: | paaljoachim | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | Quick/Bulk Edit | Keywords: | |
Focuses: | Cc: |
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 (13)
#3
follow-up:
↓ 4
@
10 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
@
10 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
@
10 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
@
10 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
@
10 years ago
- Milestone Awaiting Review deleted
- Resolution set to maybelater
- Status changed from new to 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.
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.