Cloned Posts also clones post status, trouble with JetPack

I’ve noticed this too and it is an annoying problem. Hope to see this fixed soon.

Yep, I’ve noticed this, too. I sent an email to the plug-in developer to see if he might be working on an update.

Any word on if this might be fixed? I never heard back from the developer, but I was hoping someone else had. It “ruins” a GREAT plug-in if I have to manually do all of the social media posting for each copied post…

I tried emailing the developer a couple of times, but never heard back. It seems like it would be an easy fix from his end if he wanted to fix it.

Hi all, I’m very sorry for the delay, I’ve been really busy and couldn’t work on my plugin until now.

I’m testing the plugin on WP 3.6 with the latest Jetpack, and the behaviour seems to be the following (I hope that you guys can confirm this)

1. if you “Clone” a published post from the post list AND the option “Copy post/page status” is set, the new post gets published and shared, which may be wrong as well, but I’ll skip this by now
2. if you copy to a “New Draft” either from the edit screen or from the post list, or by the “Clone” link with the above opttion unset, when you publish the draft it doesn’t get shared: but this doesn’t happen because the original post was already published, since that status doesn’t get copied. It happens because all custom fields are cloned, included the ones used by Jetpack Publicize to mark the posts already shared.

So the solution is to add “_wpas_done_all” to the fields that must not be copied in the Options page.

I hope this solves: if so, I’ll try to add an option to make it easy (so you just have to tick a checkbock to ensure Jetpack compatibility).

Awesome! Adding “_wpas_done_all” to the “Do not copy these fields” line on the Duplicate Post Options page definitely seems to have done the trick. Thank you for the help!