Duplicating meta_keys

Hello @wbenterprises ,

The ‘_cdp_origin’ key is created to track the origin of copied posts. For example, when you duplicate the ‘Hello World’ post, a ‘_cdp_origin’ meta key is created, linking the new post to the original one as its source.

Regarding why posts keep multiplying the ‘_cdp_origin’ meta keys in the WordPress database with this plugin:
This occurs when you copy an already copied post. The ‘_cdp_origin’ meta key is created multiple times, not just once. If you copy a copy, it will create 2 ‘_cdp_origin’ meta keys. If you copy a copy of a copied post, it will create 3, and so on.

Can these be safely cleaned up?
Yes, removing these meta keys will not cause any problems, as they are primarily used for renaming posts and tracking the original post, as mentioned above.

Do they go away when the plugin is uninstalled?
Currently, no. However, we will update the uninstall script to delete these meta keys upon plugin uninstallation in a future update.

We appreciate your feedback, as it helps us improve the plugin. If you have any further questions or concerns, please don’t hesitate to ask.

What purpose does this key serve for the plug-in since the end-user does not see it?

And, why is it necessary to have all the previous ones retained instead of just the most recent one?

Do you realize this could result in hundreds of entries? There’s no reason for this many entries.

If it is necessary to have the information, it should be stored in one array in one meta key, not single data points in many meta keys. It is messy.

• This reply was modified 2 months, 3 weeks ago by wbenterprises.
• This reply was modified 2 months, 3 weeks ago by wbenterprises.
• This reply was modified 2 months, 3 weeks ago by wbenterprises.

Hey @wbenterprises ,

The reasons for that are additional features of the plugin, such as Cleanup of duplicates – under the plugin section “Delete duplicate posts/pages”, or Reference to the original, under plugin section “Other options.

Kind regards

You should still convert it to an array and a single database entry. It’s not like this feature is used very often. Also, it still doesn’t explain why so many entries are required for a single post.

Thank you for your feedback @wbenterprises . We’ll consider this optimization opportunity.

Kind regards