Cloned Posts also clones post status, trouble with JetPack

  • Resolved bretpnelson

    (@bretpnelson)


    11 years, 3 months ago

    Using WordPress 3.5, JetPack Plugin-> Publicize to generate Tweet, Facebook update from post as it is published. Cloning new post from old imports the already Tweeted/posted update from the post, so it can’t be edited to generate a new Tweet for the newly published post. Just shows the original Tweet, even though the post is now new content and should have a new url. Ideally I’d like to clone the post, update the content, and send a new Tweet when I publish the new post. Discussed this at length with Jetpack support folks, who suggest:
    “The plugin seems to duplicate the content, but also the Post Status. This will indeed cause Publicize to stop working, because it will be disabled when a post has a “Published” status.”
    Thanks!
    Bret

    http://wordpress.org/extend/plugins/duplicate-post/

Viewing 6 replies - 1 through 6 (of 6 total)
  • kpont

    (@kpont)

    11 years, 3 months ago

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

    Brian

    (@brianjamesfreeman)

    11 years, 1 month ago

    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.

    Brian

    (@brianjamesfreeman)

    11 years ago

    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…

    Brian

    (@brianjamesfreeman)

    10 years, 10 months ago

    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.

    Plugin Author Enrico Battocchi

    (@lopo)

    10 years, 8 months ago

    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).

    Brian

    (@brianjamesfreeman)

    10 years, 8 months ago

    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!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Cloned Posts also clones post status, trouble with JetPack’ is closed to new replies.

Tags