Hey there, is there any way to not automatically create a topic for every blog post we publish on our website yet still keep the discussion section? I feel it makes more sense to generate a topic automatically as long as there’s a comment on a certain blog post. Currently the logic is that the topic should exist before people can comment. Thanks in advance!

That’s unusual. I confirmed locally it was working great after my latest round of fixes. Is there anything in your /logs output you could share here? I’m curious what the error is.

To be clear that we are not using any comment system other than Discourse. So what we want is to create a topic only when there is actually a comment on a post instead of a bunch of empty topics on Discourse like below: [image] Did I make myself clear? Is there a setting for this?

[image] Jamie_Liu1: Did I make myself clear? Not really… How are users supposed to reply to a topic if it’s not already posted somewhere? Every topic has to start with 0 reply. I guess I’m missing something here :thinking:

[image] Jamie_Liu1: So what we want is to create a topic only when there is actually a comment on a post instead of a bunch of empty topics on Discourse like below: I think that what you want is have all topics that are pulled to Discourse from your website be marked as unlisted. When a topic receives a comment, it would automatically be marked as listed. Unlisted topics do not appear in the topic list, so this would prevent the topic list on your site from being full of topics with no responses. This type of configuration makes sense for sites where people are accessing Discourse topics by clicking a “Start Discussion” link that is displayed below a blog post. Discourse does not have a setting for this, but I think it would be a reasonable feature request. The DIscourse WordPress plugin has this functionality, but it uses the Discourse API for unlisting and listing the topics.

@simon That’s exactly what we want! Thanks for your reply. The problem is that our site is not built with WordPress. But we can take a look at the Discourse API. Speaking of feature requests, where can I raise this request for Discourse?

@Canapin So we want the blog post to receive a comment first BEFORE it is listed as a Discourse topic. The post does exist on our site in the first place, doesn’t it?

[image] simon: I think that what you want is have all topics that are pulled to Discourse from your website be marked as unlisted . When a topic receives a comment, it would automatically be marked as listed . Unlisted topics do not appear in the topic list, so this would prevent the topic list on your site from being full of topics with no responses. That’s a good idea. The other option is to not create the topics until the user clicks through but I think your suggestion might be easier. Perhaps @eviltrout could consider this as a possible task for this release, next week?

And how can I set the Unlisted by api，I can’t find the relative apis in my comment embedding.js. Thank you.

[image] nianiaJR: how can I set the Unlisted by api The easiest way to figure this out would be to try unlisting and then listing a topic through the Discourse user interface while following the steps outlined in this guide: How to reverse engineer the Discourse API. To automate the process via the API, you would need to setup a webhook to listen for post events. When you receive a webhook telling you that the first post in your embed category has been created, you would then send an API request to unlist the topic. When you receive a webhook telling you that the second post in a topic has been created, you would then send an API request to list the topic. As was mentioned above, a better approach might be to have the topic automatically unlisted the first time a user clicks through to the topic from a blog site. That way the first user to leave a comment would not see the topic marked as unlisted. That would be somewhat more complex to setup, but it could be done through the API by listening for click events on links to your Discourse topics.

[image] simon: I think that what you want is have all topics that are pulled to Discourse from your website be marked as unlisted . When a topic receives a comment, it would automatically be marked as listed . Unlisted topics do not appear in the topic list, so this would prevent the topic list on your site from being full of topics with no responses. [image] codinghorror: That’s a good idea. The other option is to not create the topics until the user clicks through but I think your suggestion might be easier. Perhaps @eviltrout could consider this as a possible task for this release, next week? This has been asked for years on the Embed Discourse comments on another website via Javascript topic.

Yeah I think we should do this @eviltrout. At least the easier (default unlisted, once a reply arrives it is listed?) form maybe?

Not generate topic automatically for all blog posts

Product Support

codinghorror (Jeff Atwood) April 4, 2020, 8:58am 9

That’s a good idea. The other option is to not create the topics until the user clicks through but I think your suggestion might be easier. Perhaps @eviltrout could consider this as a possible task for this release, next week?

Topic		Replies	Views
Embedding, but don't automatically create a topic until a user chooses to comment Feature pr-welcome	55	9318	January 21, 2018
WP-discourse: comments are not pulled over WordPress	21	6535	April 20, 2017
[PAID] Avoid topic creation when blog posts are loaded Marketplace embedding	6	712	February 15, 2024
An idea for more economical comments? WordPress	16	1434	December 11, 2023
Create topic when a link is clicked Product Support	3	2515	September 30, 2019

Not generate topic automatically for all blog posts

Related topics