Wordpress Plugin - Duplicate Posts When Syncing

Hi All,

So the Patreon Wordpress plugin has been operating as intended with the one issue of importing duplicate posts. On initial sync it made between 5-8 copies of every post. After cleaning up the initial sync I turned off auto-publishing and disconnected/reconnected the plugin with Patreon in hopes that might help. The next two syncs also resulted in duplicate posts, albeit less than previously (2-3 duplicates each).

Not sure what to try, I have searched the Patreon Developers forum and have not found any similar issues with posts, only with images.

For reference:
WP 5.7.1 with PHP 7.3.27
Patreon WordPress 1.7.4 with API v2

Your Patreon integration health is great!

Recent connection errors:

0.41 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received

0.48 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5001 milliseconds with 0 bytes received

0.54 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received

0.8 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5001 milliseconds with 0 bytes received

0.87 days ago

get_posts - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received

0.87 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received

0.87 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5001 milliseconds with 0 bytes received

0.88 days ago

get_posts - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received

0.88 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5001 milliseconds with 0 bytes received

0.96 days ago

get_posts - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received

0.96 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5001 milliseconds with 0 bytes received

0.96 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received

0.97 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5001 milliseconds with 0 bytes received

1.39 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received

1.4 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received

1.68 days ago

delete_client - API v2 Class - UUID 1f7ac30e-059b-495c-bb48-0abb22d4489d - Response code: 204 Response :

1.8 days ago

get_posts - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received

1.87 days ago

get_posts - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received

1.88 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5001 milliseconds with 0 bytes received

2.22 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received

2.31 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 out of 0 bytes received

2.31 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 out of 0 bytes received

2.31 days ago

get_posts - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 out of 0 bytes received

2.31 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 4278 bytes received

2.31 days ago

get_post - API v2 Class - WP error message cURL error 28: Failed to connect to www.patreon.com port 443: Connection timed out

2.31 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received

2.31 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 out of 0 bytes received

2.32 days ago

get_posts - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received

2.67 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received

2.71 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received

2.76 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received

3.85 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5001 milliseconds with 0 bytes received

4.23 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received

4.36 days ago

get_posts - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 out of 0 bytes received

4.36 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 out of 0 bytes received

4.36 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 out of 0 bytes received

6.24 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 out of 0 bytes received

6.24 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5001 milliseconds with 0 bytes received

6.24 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 out of 0 bytes received

6.24 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received

6.24 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 out of 0 bytes received

6.24 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received

6.24 days ago

get_post - API v2 Class - WP error message cURL error 28: Operation timed out after 5000 milliseconds with 0 out of 0 bytes received

The plugin detects similar posts either by the specific meta it adds to new posts, or, if the posts exist, by checking exact same title.

If there is any plugin or custom code in your WP site that modifies metas or the titles, that may cause the plugin to miss detecting existing posts. That may be worth looking.

Also, things like opcache or redis, when not refreshed properly, may cause odd behaviors like these.

The Patreon Plugin does not import duplicates of past posts, it only creates duplicates of new posts, so I do not think it has to do with a conflict with meta information (nor do we have anything changing meta information on posts).

I will take a look into opcache and/or redis shortly to see if I can refresh that and see if any other plugin is conflicting with the Patreon plugin but if this info brings up any new ideas please let me know!

Thanks,
Hean

This sounds like somehow 2 webhooks for post sync was created at Patreon. May happen if you clicked twice during setup or another time while the earlier request was going on.

You may try to disable post sync to attempt deleting the webhook. This may or may not delete one of them. If it does, it should solve it.

Unfortunately patreon.com doesnt show programmatically created webhooks below so you cant manually delete it: