# 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:** 3

<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:** [July 20, 2020, 4:24pm UTC](https://meta.discourse.org/t/how-does-discourse-replace-wp-comments-exactly/157969/3 "2020-07-20T16:24:54Z")

</div>

> [@Kayla](#):
>
> I have Toolset Access control on a custom post type that is posting to Discourse (to a private category that aligns with the access control). Normally this type of control would also affect visibility of the post comments, but it’s not affecting the display of the Discourse comments.

The [WP Discourse](https://github.com/discourse/wp-discourse) plugin displays comments by loading a custom comments template. It uses the WordPress `comments_template` filter to load the custom template. I’m not sure why the comments are still loading when you have Toolset Access control configured for a post type. I’ll look into what is going on with that.

I think the plugin should add an option to not load comments for posts that have been published to a private Discourse category. When enabled, just a link to the Discourse topic would be displayed. I’m not sure that would solve the issue you’re dealing with though.

---

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