This guide will show how to set up comment embedding on your own blog or web site.
How it works
In Discourse, a topic is made up of many posts. When you are embedding Discourse on another site, you are linking a document (blog entry, HTML page, etc.) with a single topic. When people post in that topic, their comments will automatically show up on the page you embedded it in.
You have the choice to have Discourse create the topics automatically when a new embedding is found, or you can create the topics yourself in advance.
Configuring Discourse for Embedding (simple setup)
The following setup will embed a comment feed on a page on a fake blog URL of
http://example.com/blog/entry-123.html, from a discourse forum running at
Visit Admin > Customize > Embedding on your Discourse install.
Create at least one embeddable host. This should be the hostname (domain) where you want to embed your comments. In this case the host is
example.com– note the lack of
Class Name is a class name that will be attached every time your iframe is rendered. You can use it for styling purposes.
Path Whitelist allows you to specify the paths on the remote host that would accept your embed.
Post to Category - if you supply a category alongside the host you are entering, posts imported from that host will automatically end up in that category. Different hosts can post to different categories.
Fill in the name of a user on your discourse who will create topics in the
Embed by Usernamefield. Let’s assume our discourse has a user called eviltrout, so the value is
Insert the following HTML on the web page at
The configurable parts of the snippet are in the
discourseUrl is the full path to the base of your discourse, including the trailing slash. The
discourseEmbedUrl is the document that is currently embedding a comment feed.
If you set this up correctly, the first time you visit
http://example.com/blog/entry-123.html it will try to load comments for the blog post. Since there are none, it will tell the Discourse forum to create a new topic in the background. A new topic will be created by
eviltrout and the contents of the first post will be crawled from your blog and the text will be extracted automatically.
Once the new topic is created, users can post on it, and their comments will automatically be displayed the next time
http://example.com/blog/entry-123.html is visited.
Embedding on more than one page
In the above example we hard coded our
discourseEmbedUrl with the current page’s URL. On my blog, I use the following value for
'http://eviltrout.com<%= current_page.url %>' – as new blog pages are created, new topics will be created for them automatically on Discourse.
Styling your Embedded content
If you are running Discourse 1.4.0 or greater, you have the ability to add a stylesheet for your embedded comments. Visit Admin > Customize > CSS/HTML > Embedded CSS and you can add a custom stylesheet that will be served up with your embedded comments. By default we think the layout looks nice on a white background, but if your site has a unique layout you’ll want to style it yourself.
(Optional) Adding a Feed for Polling
As mentioned above, Discourse will automatically crawl any site it is embedded on. However, sometimes HTML can be hard to parse and it might not extract the contents of your posts correctly. Many blogs and web sites support RSS/Atom feeds for syndication, and Discourse can use this to extract the content of your blog posts more accurately.
If you have a RSS or Atom feed set up on the site you are embedding Discourse into, you can configure Discourse to extract the content of posts from there by enabling the setting
feed polling enabled and then providing the full URL to the feed in the
feed polling url setting.
(Alternate Configuration) Linking to existing topics
Some people prefer to not have Discourse create topics for them automatically on their forums. They’d like to create the topics themselves, then simply tell their embedding code what topic they want to associate with. You can do this by slightly changing your embedding code:
The only difference here is we’ve replaced
discourseEmbedUrl with the id of a topic from Discourse. If you do this, no topic will be created and the comments from that topic will automatically be displayed.
Embedding comments from a private site
For private Discourse instances, if Discourse is on a subdomain of the blog’s domain, comments will be displayed for users who are logged into Discourse. Users who are not logged into Discourse will see a ‘refused to connect’ message. If Discourse and the blog are on completely separate domains, no comments will be displayed for private forums.
The most common issue users have when embedding Discourse is setting the correct value for the embeddable hosts you added. Make sure to double check that it is only the domain of your site, and contains no extra slashes or invalid characters.