I have a head-scratcher that I can’t seem to figure out. From what I see, post id’s are not always syncing across to our Discourse site (forum.pistolsfiringblog.com) from the Wordpress site (pistolsfiringblog.com) causing comments to fail loading on the Wordpress posts along with the option to comment (we do not allow WP comments, only Discourse). A good example is the following post: WP: Coleman Scott Joins Oklahoma State Wrestling Staff as Associate Head Coach Discourse: Coleman Scott Joins Oklahoma State Wrestling Staff as Associate Head Coach - #4 by MiggityMac - PFB Articles - The Chamber Even though comments are allowed on the post, the post_id is coming across undefined. I did a little diving into the Discourse Wordpress plugin and it just returns when id is undefined. That’s fine and to be expected. Nothing stood out. However, other posts on the site display comments while others do not. The settings are the exact same as the no-show posts (I’ve intently compared). If I try to force the id into the webhook call https://pistolsfiringblog.com/wp-json/wp-discourse/v1/discourse-comments?post_id=259952 I get: "\t\t \n\t\t\t \n\t\t\t\t Comments are not currently available for this post. \n\t\t\t \n\t\t \n\t\t" …Which is completely not true. They are available and they are allowed. For whatever reason beyond me, I can not see my certain posts are not getting a post id to link/relate to the corresponding discourse post so that comments can flow across to WP. To complicate things, I did a test post as one of our editors would do and watched the entire process from WP post to Discourse and back to WP even with additional comments from Discourse. They all sync’d back to WP on my test post. I’ve attached screenshots of the main issue (not limited to just one post). Any help is highly appreciated. At this point, I am at a complete loss. ¯\_(ツ)_/¯ [Screenshot 2023-08-21 at 21.52.16] [Screenshot 2023-08-21 at 21.50.00]

Hi @MiggityMac, I’m having a look at your site and I notice a lot of console errors that appear to be related to google ads. Something crashed my browser there too on the Wordpress page. Also seeing content policy and permission errors on the Forum side of the embedded commenting even when the comment button is functional and you can go to the comments. I’m not sure at this point, but it’s possible some of the ad related errors are causing issues that are conflicting with the plugin. I’d review the content security policy settings because that can cause embedding issues. I run the Wordpress plugin on our forum and the few times we’ve had issues with embeds or the button appearing on the Wordpress page, it’s been the content security policy settings. On pages where the comment button works, I still see errors on both sides (Wordpress and Discourse) . I’ll continue to have a look and do some digging… This is in Discourse on one of the ones that worked [wp-discourse_errors]

@MiggityMac have you had a look at the WordPress logs? [image] View logs for the WP Discourse plugin Administrators The WP Discourse plugin has its own logging system (since v2.2.5). This is an overview of how it works and how to use it. If you have any questions please respond below. What is logged All of the main WP Discourse feature-sets log errors (since v2.3.5). To log every action, including successful ones, you can turn on verbose logging for the relevant feature-set you want more information on. Look for a setting starting with “Verbose..” in the relevant settings tab. How logs are stored The plugin…

Thank you much, @Lilly - I wasn’t able to dive deep into yesterday, but today/tomorrow I will be. This is very helpful. I’m going to get into the logs soon and see what’s happening there.

[image] Lillian : I’d review the content security policy settings because that can cause embedding issues. Did the Wordpress plugin start embedding at some point? Last I checked it was syncing copies of comments and displaying them locally.

Here are the most recent WP Discourse logs: pistols-firing-wp-discourse-logs-2022-06-01-2023-08-23.zip (159.7 KB)

Apologies @Stephen you are correct and I am just getting some terminology mixed up. I do know how the plugin works.

[image] Michael: From what I see, post id’s are not always syncing across to our Discourse site (forum.pistolsfiringblog.com) from the Wordpress site I’m curious about what’s going on with this, so figured I should have a look. There are lots of 429 (too many requests) errors in your logs. Those errors are being called when WordPress attempts to pull a post’s comments from Discourse. I’m not finding errors related to the post you’ve linked to, but possibly the error logs are getting flooded and some errors are skipped. Here’s a Discourse topic and WordPress post that I’m finding errors for: Three Questions for Oklahoma State's Offense Entering Fall Camp - PFB Articles - The Chamber Three Questions for Oklahoma State’s Offense Entering Fall Camp The easiest way to start debugging the issue would be for you to go to that post’s edit page on WordPress and enable the “custom fields” panel: [image] [image] That should display some fields that look like this: [image] I suspect there will also be a ‘wpdc_sync_post_comments’ field with its value set to 1. If for some reason it’s stuck at 1, that would explain all the ‘too many requests’ errors. Also, on the WordPress plugin’s Commenting settings tab, what’s the value of the “Enable Discourse Comments” setting? [image] Has getting Discourse comments to display on your WordPress site ever worked for you? If so, can you think of anything that might have been changed on the WordPress site when comments stopped displaying?

Thanks for this great info. Discourse Comments used to work fine until we had a problem with Raptive (ad thrive updates). The Discourse commenting settings are the same that you’ve screenshoted. I enabled the custom fields are on a post. I don’t see any of the fields on a different post, but I do see the on the post in refernce. The wpdc_sync_post_comments was set to zero. [image] [image] I’ll get the meta on a ‘broken’ post this morning.

@simon - here’s the post meta of a broken post (found here: Arizona State Reportedly Names True Freshman Jaden Rashada as Starting Quarterback) [image] AND the Post Data (split shots): [image] [image] And some errors in the DC logs (but that is from me updating it previously): [2023-08-24 19:50:18] publish.ERROR: create_post.post_error {"wp_title":"Arizona State Reportedly Names True Freshman Jaden Rashada as Starting Quarterback","wp_author_id":"20980","wp_post_id":260073,"response_message":"Embed url has already been taken","http_code":422}``` Does this help?

Issues with Raptive Ads

Product Support WordPress

angus (Angus McLeod) August 22, 2023, 6:58am 4

@MiggityMac This is where I’d start. Lily’s CSP suggestion is also a good one. Also, if possible, could you share the wp meta fields saved in the WP database for that example post?

Topic		Replies	Views
Discourse not linking the Comments automatically under the articles WordPress	30	1538	January 15, 2025
The link to the comments community is missing from the Wordpress article WordPress	9	387	June 15, 2025
Configure WP Discourse to display comments from Discourse Administrators wordpress , video , how-to	10	3733	June 25, 2025
WP-discourse: comments are not pulled over WordPress	21	6512	April 20, 2017
Comments are not showing after post content WordPress	27	8774	April 29, 2025

Issues with Raptive Ads

Related topics