I just published a new WordPress plugin to embed Discourse comments using Discourse Embed code. https://github.com/techAPJ/wp-discourse-embed This WordPress plugin injects the Discourse embed code in blog posts, allowing you to use Discourse as community engine. It takes two options: [imagem] Discourse URL should be the URL of your Discourse instance, this field is required. Embed Discourse comments on posts published after date is an optional field, if provided only blog posts published after the date you specified will use Discourse comments (hiding the original WordPress comments). Blog posts published before the provided date will use original WordPress comments. That’s it once you have activated the plugin and provided Discourse URL, you should start seeing Discourse comments embedded under your blog posts! If you want to show comment count under each topic on blog front page, then add this HTML snippet (in your theme index file) under topic markup: #discourse-comments">Discussion The above snippet will show as: Discussion (8 replies) Where 8 is the reply posts count for that particular topic. This plugin also adds author nickname in meta tag, like: Where techapj is WP nickname of post author. This plugin assumes that you have already configured embedding settings as instructed here. Download the plugin, and start contributing! – GitHub - arpitjalan/wp-discourse-embed: WordPress plugin that lets you use Discourse as the community engine for a WordPress blog · GitHub

How is this plugin different from wp-discourse? They literally have the same introductory description, which is very confusing. This WordPress plugin allows you to use Discourse as a community engine for your WordPress blog. I guess it has something to do with how wp-discourse requires API access, whereas wp-discourse-embed is “lower commitment” with no API key needed, working more like the “paste-and-you’re-done” type of embedding you get from the likes of Disqus. Sound about right? Would definitely appreciate more clarification though. What are the different use cases? What’s the overlap (do they have the same strategy for styling comments?). If this could work like Reddit embeds, that’d be super cool. As in: I write a blog post I announce the blog post on a DIscourse forum like Meta I embed my Discourse topic into my blogpost, effectively using Discourse for comments without hosting it myself.

[imagem] erlend_sh: How is this plugin different from wp-discourse? The wp-discourse-embed plugin uses the Discourse Embed code. Here are the pros and cons as compared to wp-discourse plugin: Pros: Requires minimal configuration Comments HTML is auto created, so styling is not required. Can enable Discourse comments only on posts published after specified date. Cons: Not much customizable, hence less features. Comments HTML can not be styled as per the theme. wp-discourse-embed is basically a WordPress plugin for: [imagem] Embed Discourse comments on another website via Javascript Integrations Discourse has the ability to embed the comments from a topic in a remote site using a Javascript API that creates an IFRAME. For an example of this in action, check out Coding Horror’s blog. The blog is run via Ghost but the comments are embedded from his Discourse forum. One important thing to note with this setup is that users have to navigate to your forum to post replies. This is intentional, as we feel that the posting interface on a Discourse forum is currently much richer than what we … [imagem] erlend_sh: I embed my Discourse topic into my blogpost, effectively using Discourse for comments without hosting it myself. This is not possible because the blog hostname should be present in Admin > Customize > Embedding.

To fix published date and author for topics linked to old WP posts see: [imagem] Fix published date and author for topics created via wp-discourse-embed plugin WordPress I recently installed wp-discourse-embed plugin on Quarter to Three WordPress blog. As soon as I installed the plugin there was an influx of new topics being created for existing (old) WP posts. I ran this rake task to fix the published date and author for topics that are linked to old WP posts: desc "Fetch WP data" task "users:fetch_wp_data" => [:environment] do puts "Fetching WP data" i = 0 TopicEmbed.find_each do |topic_embed| begin html = open(topic_embed.embed_url).read …

I’m just adding a note here about an issue that was reported last month with comments not being displayed due to recent changes in how many browsers are now setting the referrer policy for cross site requests. That issue has been fixed in the core Discourse code. As long as your Discourse site is running the latest code, you should be able to use the WP Discourse Embed plugin without any issues. For more details about the issue, see https://meta.discourse.org/t/embedding-discourse-comments-via-javascript/31963#setting-the-referrer-policy.

WP Discourse Embed Plugin

Product Support WordPress

techAPJ (Arpit Jalan) 3 Setembro , 2016 18:50 4

To fix published date and author for topics linked to old WP posts see:

Tópico		Respostas	Vistas
Reply to comment directly on WordPress vs. Linked to Discourse topic WordPress	4	215	24 Julho , 2026
Comments not being embedded in wordpress plugin WordPress	11	3712	20 Maio , 2016
How to enable Discourse comments via JavaScript in Wordpress? WordPress	5	3014	20 Novembro , 2017
Discourse comments are not reflected on Wordpress blog WordPress	2	2113	26 Setembro , 2017
Configure WP Discourse to display comments from Discourse Administrators wordpress , video , how-to	10	3678	25 Junho , 2025

WP Discourse Embed Plugin

Related topics