# Embedding, but don't automatically create a topic until a user chooses to comment

**URL:** https://meta.discourse.org/t/embedding-but-dont-automatically-create-a-topic-until-a-user-chooses-to-comment/61450
**Category:** Feature
**Tags:** pr-welcome
**Created:** [9월 23, 2015, 9:03오전 UTC](https://meta.discourse.org/t/embedding-but-dont-automatically-create-a-topic-until-a-user-chooses-to-comment/61450 "2015-09-23T09:03:12Z")
**Posts on this page:** 1
**Showing post:** 34

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [6월 15, 2017, 1:58오전 UTC](https://meta.discourse.org/t/embedding-but-dont-automatically-create-a-topic-until-a-user-chooses-to-comment/61450/34 "2017-06-15T01:58:11Z")

</div>

We encountered the excess post load problem, but the other way around. [Having WordPress poll ~15k posts for updated comment counts via the plugin caused crazy scaling issues on the remote host](https://meta.discourse.org/t/server-scaling-and-load-created-by-the-plugin/38821/).

That said, we found value in having the stubs in Discourse, and they didn’t create substantial noise as the category article comments fell into was suppressed from the front page using the ‘Suppress this category from the homepage’ option. The titles were usually descriptive enough that search would find the stubs, and direct the users back to pages on the content site.

> [@sam](#):
>
> it should just be the default behavior, it is far safer

It may be that for knowledge sites this setting is preferable, but for content entities the stubs almost certainly have value, particularly when the plugin embeds the excerpt and link back to WP. @simon has some approaches in mind to tackle the issue of load, at least on the WordPress side.

---

_[View the full topic](https://meta.discourse.org/t/embedding-but-dont-automatically-create-a-topic-until-a-user-chooses-to-comment/61450)._