The discussion revolves around the “Comment formatter errors in logs” issue. haydenjames shared their logs, which show a mix of successful sync comments and error messages, specifically comment_formatter.ERROR: format.missing_post_data {"keys":"discourse_comments_raw"}.
gizadev is experiencing a similar issue, with the error occurring every 2 seconds, causing slow PHP processes and a FLOCK that brings their site down repeatedly. angus acknowledged the logging issue and plans to address it. However, angus is unsure if WP Discourse is the source of gizadev’s issues, as they may be related to other sources.
angus asked haydenjames to check their logs for the warning again, suggesting that the logging might be accurate but needs additional data. haydenjames reported no issues since disabling the logs, but later found error messages from April 30th.
I have the same issue with comment_formatter.ERROR: and don’t even have comments from discourse turned on, nor ajax. It hits the logs ever 2 seconds round the clock. Meanwhile a lot of slow PHP processes and an FLOCK that halts everything, bringing the site down repeatedly.
@gizadev Thanks for the report. We’ll be addressing the logging issue soon (it’s at the top of my list this week).
Just a note that I have a few doubts as to WP Discourse being the source of your issues which sound like they may be at least partially related to other sources.
Did you previously have them enabled and do you have existing Discourse comments on your Wordpress?
If possible, could you share your WP Discourse logs with me privately.
@haydenjames Just following up on this, would you be able to check your logs to see if that warning has cropped up again?
Looking at it again now it seems the logging is accurate, albeit it should be a warning rather than an error, and it needs additional data (like the post causing it), however I’m not sure I’m capturing all scenarios in the test.