Thanks, appreciated the feedback.
We’ve signed up for the trial as you suggested and were able to reproduce the issue.
We found out that even renaming $post to $local_post or similar doesn’t solve the issue. The only workaround we found is to json_encode and then json_decode the content, as to create a completely separate object. Very ugly.
Nevertheless, we published an update to solve this incompatibility, even if the previous design was 100% correct from a code standpoint.
Here’s the patch that has already been published
- unset($post->post_content);
+ $json = json_encode($post);
+ $local_post = json_decode($json);
+ unset($local_post->post_content);
if ($post->post_status === 'publish') {
if (!get_option('lnkbio_id') || !get_option('lnkbio_secret')) {
return;
@@ -138,7 +140,7 @@ function lnkbio_api_sync($post_id, $post, $update) {
'body' => [
'ACTION' => 'WP_sync',
'post_id' => $post_id,
- 'post' => json_encode($post),
+ 'post' => json_encode($local_post),
'id' => get_option('lnkbio_id'),
'secret' => get_option('lnkbio_secret'),
'permalink' => get_permalink($post),