Social Network Auto Poster interoperability

I saw https://ww.wp.xz.cn/support/topic/repost-with-jetpack-publicize/ in the forum.

After doing some digging, I found that SNAP sets the date (in seconds-since-epoch format I believe) that the post is autoposted in wp_postmeta meta_key “snap_isAutoPosted” Then when SNAP gets fired by the post getting re-published, it checks and finds that it was already posted independent of the post date being updated, and skips autoposting. Here’s the SNAP log: (note: read from bottom up)

[2019-05-22 13:59:27] – [Skipped]- Already Autoposted (on 2019-01-18 13:10:14) – Post ID:(2122)
[2019-05-22 13:59:27] – [Start =- ]- ——=========#### NEW AUTO-POST REQUEST ####=========—— PostID:(2122) Immediate
[2019-05-22 13:59:27] – [*** ID: 2122, Type: post]- Status Changed: draft_to_publish. Autopost requested. 0

So, I think that in order for APS to work with SNAP, it must either reset or remove the wp_postmeta:snap_isAutoPosted key/value. There is also a snapFB key as well, it may need to be reset/removed.

I’ve had similar issues with SMAP, but haven’t tried Jetpack’s Publicize. I noticed that there is a xyz-smap meta_key in wp_postmeta, my guess is that’s how SMAP decides whether something’s been auto-posted to social and is what’s preventing APS from working with SMAP.

The page I need help with: [log in to see the link]