Thanks for that, I’ll see what I can do to make the plugin description and settings descriptions clearer.
I’m not aware of this, but wherever it’s being advertised it should be made clear what the plugin does. My understanding is that the goal of the plugin has always been to move commenting out of the WordPress comment section and onto the Discourse forum. This is with the aim of improving the quality of discussions that occur around WordPress posts. The comments that are displayed underneath a WordPress post are meant to function as a ‘teaser’ to get people to join the discussion on the forum.
Can’t find the source. Maybe it was just my own wishful thinking or someone else somewhere explained it wrong. That’s why I put “advertised” in quotation marks. But I’m glad you see my point.
As for the overall aim of improving the quality of discussion: if you are implying that it’s not just technical reasons why people can’t comment on the spot (i.e. under the post) but that it is actually intentional to drive people into the forum, then I’m not sure I’d agree with that aim. Of course, increasing the quality is good, but the way WP-discourse currently works, there is a high price to be paid for this: people have to login to comment (or did I miss something again?) which means you probably lose a significant number of comments. Not from those who have an account, but from passers-by who couldn’t be bothered to create an account.
I definitely don’t want to lose those comments and so I am currently trying to come up with the best way to set this up. Here are some thoughts:
Two reasons why I hesitate to use discourse as my only commenting tool: a) I don’t think I want to publish all posts/pages on the forum (but that might be because I’m not sure what that would mean in practice) and b) because I don’t want to lose those passer-by comments.
Currently, this apparently means that I need to decide whether I should a) not use discourse on WP at all, b) use it side-by-side with WP comments, or c) use it side-by-side with some other commenting plugin (such as Replyable by Postmatic)
Ultimately, none of these three options are satisfactory. a) would just be a pity, b) looks confusing (if not ugly) and c) is probably even worse than b). Both b) and c) just don’t make sense in the long run, because why should you maintain two commenting systems.
I will have to explore b) and c) further but what I really want to say: I think it would be worth developing the plugin so that option d) becomes viable: use only discourse for comments. My hunch is that a good way forward would be to provide a simplified commenting box under each WP post that does not require login. Or perhaps, rather than providing your own box just use the WP commenting function and pull over all approved comments to WP (and pull over the post too, if necessary). If the email address under which the comment was submitted does not exist in discourse, it automatically creates a user account and posts the comment under that account.
I don’t think there are any plans to make the core of the wp-discourse plugin do what you are asking, but most of it is technically do-able.
Right now we’re working to make it easier to extend the wp-discourse plugin with other plugins - allow them to share the options pages etc.
After that work is done, a plugin could be made to add a comment box to the bottom of WordPress posts that would post the comments to Discourse. To do this, the WordPress post would still need to be published to Discourse.
The idea of turning Discourse comments into WordPress comments is interesting, but it’s not the way the plugin works - it treats the Discourse comments as post_metadata and leaves the WordPress comments alone.
A partial solution would be to not select the ‘Use Discourse Comments’ setting, but to publish some of your posts to Discourse so that a discussion could occur there as well. That would give you something like this:
We value quality over quantity. You may have noticed comment fields are undergoing a bit of turbulence these days. We are of the opinion that “drive-by comments” promote low quality discussion, therefore we are unlikely to ever have built-in support for that in our canonical products.
I don’t think combining Discourse comments with other comment solutions is a good idea. Either use Discourse or a different comments system altogether. If you prefer something forum-like, Muut is pretty good.
Yes, this is exactly the direction my thoughts were heading. Now, if it were possible to put that link (join the discussion in our forum) under every WP post, without the post being published on discourse, that would be an huge improvement. In other words, what I’m suggesting is that it is someone clicking on that link that would trigger the post being pulled over to discourse.
An unintended but positive side effect of that would be that even if the user ends up not leaving a comment, you they did indicate their interest in the discussion and and that can be valuable information in itself. To elaborate the idea, there could be an option to not actually publish the WP post on discourse unless it actually receives a comment. And spinning that train of thought further: perhaps the easiest way to implement this would be by using the existing function to publish all posts on discourse but to keep them hidden until they receive a comment.
Okay, I am starting to reconsider my wish to capture drive-by comments. Thanks for pointing out Muut. It is indeed an interesting project but for various reasons I prefer to stay in the open source realm. One might also mention nodeBB and Flarum here, although I haven’t figured out exactly how well the work with WP. In the case of Flarum it is probably to early to look for such an advanced feature.
I’m also looking for a plugin which is doing the following:
Deactivate comment function in Wordpress
SSO (sign in in Wordpress, autosignin in Discourse)
When creating a new article in Wordpress, i’d like to choose the correct Categorie and the exact Board in which i want the topic for the discussion to be opened
I want to set the title for the topic inside my blog-post creation mask
At the end of my blog post, there should be a button which says “XXX Comments” and is a href directly into the discussion.
The Topic should contain the first 250 characters of my blog-post (Textarea, for Copy & Paste) and a button “[…] read more” which redirects to the article
Discourse should be a part of my site, my theme, whatever and not a standalone solution. The user should see my top navigation, and maybe my own sidebar. I only want the topics / categories to be displayed in a smart, mobile and optical good way
As far as is searched the whole web for that, no software is actually able to do the exact thing i described above
Maybe we can crowdfund sth like this? x) Or there is a developer out there, who will do this?
If you want users to come back and visit your site again, you need them to interact with your site. BBPress is not usable for me, as it is only total standard. Having users discuss about articles inside a forum like discourse, with such great features, would realy be a overvalue!
Of course i checked it out, but the fact, that discourse boards are not part of my site is a thing, i can’t deal with. I want the topics be part and integrated into my site. The user should see the header and my sitebar and in my content-area, there could be the discoures boards.
It should look like it looks if you integrate BBPress… just as one site.
[quote=“Sanafan, post:18, topic:57232, full:true”]
Christoph forum.driveonwood.com did a trick…they rebuild the header from the main site… no drop-down inside the forum, and its smaller. [/quote]
I didn’t notice the missing dropdown menu. Well spotted. If it is important to you, I guess it could be added manually. But I agree that it is a disadvantage not to be able to use the original wordpress menus/ nav bar. But it looks like this won’t change any time soon in discourse.
As for the size, I don’t know why they didn’t adjust the size to be equal. Probably too much hassle for something nobody notices.
Visual composer would be a rather specific choice, but a more generic solution already exists in the form of the WP-discourse-shortcode plugin I referred to earlier. I haven’t tried it, but you should be able to paste that the desired short code into a text box in the pagebuilder of your choice (some pagebuilders even provide content elements specifically for shortcodes) and place it wherever you want. If you want it in the sidebar, your page builder wont be of any use to you anyway. In that case, you have to paste the short code into a WP text widget.
I think that would be possible to do, but it would be a fair amount of work to setup and might not give you much benefit. Have you seen the way BoingBoing deals with comments? They publish every post from their site to Discourse. They include a link to the discussion at the bottom of each post. http://boingboing.net/2017/02/21/watch-how-to-transfer-an-ant-c.html
But regardless of these sites, I’m wondering what exactly the benefit of js
embedding is on a wordpress site where I can just use the wp-discourse
plugin to display the comments.
In fact, I am starting to let go of the ides that comments should be
displayed (and written) under the blog post or page and wanting to give the
discourse way a chance. And when you do that, the wp-discourse plugin
actually gives you an interesting filter option to display only the better
comments under the post. Something that the js can’t do, apparently.
Hey Simon, I wanted to chime in with a similar request…
We’re building a membership site for guitarists. We’ll have at launch roughly 1,000 pages which each contain either a lesson video or musical example, and adding many more over time.
We’d like to have discussion of this material via Discourse — the normal comment integration seems great for this, e.g. asking questions about a specific topic or example covered. If someone has a question they can click through below to ask it on the forum. However we’d much prefer not to start with ~1,000 empty topics visible on our forum. For this use case it would make a lot of sense to have a way to either create the topic only when someone asks the first question about it, or simply hide the topics on the forum until that happens.
I found a similar question that references another older thread where a user asks:
Would it be possible to not automatically create a topic until a user chooses to comment on the article? I want to prevent having a ton of topics with no replies (i.e. which were created automatically by visitors who only read articles and not commented on them). I’m specifically thinking of a site with a large number of articles; only a few of them will actually have comments.
I see your predicament. But instead of the potentially messy solutions discussed so far, what if the topics are indeed created normally, but until they have a reply, they are unlisted, i.e. not visible in the forum stream and only accessible via a direct link. Would that be an acceptable compromise?
In other words, the basic spec request becomes something like this:
Option to set topics generated for embedded comments as unlisted by default.
Special flag that can be put on selected unlisted topics (in this case automatically) to make them unlisted if they receive a reply.
This actually sounds like a great solution, and from what I gather also easier technically than whatever sort of “staging” would be required to not create the associated topic at all until the first question is asked.
This would be awesome to have as an option in the WP Discourse plugin. I’m not sure what would be involved in making it happen but let me know. We’d love to do what we can to help make this happen.
Thanks!! I was struggling with this and your comment solved my issues. I’m setting up a new WP/Woocommerce/Discourse site, and couldn’t figure out why the comments don’t work. In retrospect it makes perfect sense that existing posts in WP aren’t automatically linked. I was just thinking that by turning on the plugin, the WP comment box itself would always be replaced. It sure would have been easier had there been something to that effect in the plug-in. Currently it says “For Discourse comments to appear on your WordPress site, you must select this setting and enable comments for the WordPress post.” I think it would be easy to add “Existing posts will not have Discourse comment functionality unless they are republished to Discourse.”
I’m also struggling with keeping two comment systems. As mentioned I’m running a Woocommerce site. I’d love to have a single commenting system (Discourse) for UI sake, but not keen on “publishing” hundreds or even thousands of product to Discourse.