Hi Angus! That’s affirmative, the “Sync Comment Data” webhook option is enabled on the WP side, and I created the webhook on the Discourse side and pings are successful. The WP plugin’s logging shows comment.INFO: sync_comments.success messages at the right timestamps:
[2025-07-07 14:16:38] connection.INFO: check_connection_status.successful_connection
[2025-07-07 14:16:38] connection.INFO: check_connection_status.valid_scopes
[2025-07-07 20:11:31] comment.INFO: sync_comments.success {"post_id":786}
[2025-07-07 20:25:03] comment.INFO: sync_comments.success {"post_id":786}
[2025-07-07 20:32:14] comment.INFO: sync_comments.success {"post_id":786}
[2025-07-07 20:44:15] comment.INFO: sync_comments.success {"post_id":786}
[2025-07-07 21:00:39] comment.INFO: sync_comments.success {"post_id":786}
[2025-07-07 21:01:42] comment.INFO: sync_comments.success {"post_id":786}
[2025-07-07 21:15:40] comment.INFO: sync_comments.success {"post_id":786}
It’s just that even with those success messages, existing visitors (or at least me, multiply testing on firefox/safari/chrome on a mac, firefox/chrome/edge on a win10 PC, and safari on ios) keep getting a cached /wp-json/wp-discourse/v1/discourse-comments endpoint, with cache-control headers set to a nonzero amount. If I do a ctrl-shift-f5 on Chrome (or the equivalent in other browsers) to force it to bypass local cache on refresh, everything works great and the new posts appear.
With the mu-plugins in place, that endpoint shows cache-control set to no-store no-cache etc, and the problem behavior doesn’t manifest—simply visiting the WP post or refreshing it with the regular refresh button shows new embedded comments.
I’ve turned on verbose webhook logging and posted a test post, and things appear OK when I create a new post:
webhook_topic.INFO: update_topic_content.update_post_metadata_success {"post_ids":"786"}
Everything seems to be working, but I still don’t really understand why the original problem behavior manifested, or if it’s arisen from some overlooked issue on my end. (Very possible!)
D’oh, sorry, I’m sure you’re right about me screwing that up — yesterday was a long day, and like I said, I’m kind of at the limit of my abilities here. It was definitely doing something, though now I’m wondering if the “fixed” behavior I’m seeing is just it being broken in a new way. (I’ve updated the “transient killer” plugin to use the right argument now, thank you!)