# How does Discourse replace WP comments exactly?

**URL:** <https://meta.discourse.org/t/how-does-discourse-replace-wp-comments-exactly/157969>\
**Category:** WordPress\
**Created:** [July 16, 2020, 7:41pm UTC](https://meta.discourse.org/t/how-does-discourse-replace-wp-comments-exactly/157969 "2020-07-16T19:41:18Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)\
**Post date:** [August 10, 2020, 9:37pm UTC](https://meta.discourse.org/t/how-does-discourse-replace-wp-comments-exactly/157969/10 "2020-08-10T21:37:23Z")

</div>

> [@Kayla](#):
>
> For posts published to private Discourse category, it seems to be loading the default WP comments form. No link to Discourse topic.

Here’s what I’m seeing when I select the " Display comments for public topics" option and the “Show Existing WP Comments” option, then publish a post with existing WordPress:

 ![image](https://global.discourse-cdn.com/meta/original/3X/7/2/72a38090ea36a6a1ff6c53fdaa79eaefa8a77d63.png)

From a user’s point of view, this doesn’t seem very clear (that could be fixed with some WordPress customization), but the link to the Discourse comments exists.

> [@Kayla](#):
>
> I updated Clear Cached Comment HTML + Force Category Update. Am I overlooking anything?

If you have enabled the “Cache Comment HTML” site setting, try disabling it. That setting shouldn’t cause an issue, but unchecking it will simplify debugging this.

Send me any more details that you have about the issue. I’ll be pushing a small update to the WordPress repo later today fo fix an issue with the “Unlink Topic” button that’s happening with the WordPress 5.5 release.

---

_[View the full topic](https://meta.discourse.org/t/how-does-discourse-replace-wp-comments-exactly/157969)._
