TL;DR: Discourse gives “Error Embedding” regardless of which hosts I allow in Embedding settings. I have a published site at foo.com which embeds comments from the Discourse forum at forum.foo.com , which his working fine. When going to e.g. https://foo.com/blog/2019-11-22/foo-0.9.6-released , I see…

[Bild] rawtaz: DiscourseEmbed = { discourseUrl: ‘ https://forum.foo.com/ ’, discourseEmbedUrl: ‘ http://localhost:1313/blog/2019-11-22-foo-0.9.6-released/ ’ }; You might want to use topicID as mentioned at Embed Discourse comments on another website via Javascript . I wouldn’t be surprised if “lo…

@maiki Thanks a lot for taking the time to reply. Using topicId as described in the guide doesn’t make it work or change any symptoms. The URL requested of course changes to https://forum.foo.com/embed/comments?topic_id=2279 instead, but it gives the exact same error message. I also tried changing…

[Bild] rawtaz: but it gives the exact same error message. What is the error message? Is there anything in the dev console? [Bild] rawtaz: For example, are requests from a localhost site blocked? localhost is not a valid domain, it’s a hostname. localhost In computer netw…

[Bild] maiki: [Bild] rawtaz: but it gives the exact same error message. What is the error message? Is there anything in the dev console? No, there’s nothing wrong in the dev console on the localhost client/browser. HTML is successfully returned from the forum server, I can see it just …

[Bild] rawtaz: Discourse gives “Error Embedding” regardless of which hosts I allow in Embedding settings. Is your Discourse site set to login required?

[Bild] simon: Is your Discourse site set to login required ? The setting named “login required” in the “Login” section is unchecked, so no, it is not.

Thinking out loud; What differs between when the request comes from my local development site, and when it comes from the production site, isn’t much. It should be just the HTTP referrer and of course the source of the HTTP request. Other than that I’m using the same browser for both sites.

You can test if it is a host issue by trying to embed it on another, live domain (perhaps a sub-domain for one you have). Me thinking out loud: if I told Discourse to accept “localhost”, it will look for it at localhost, which is the Discourse server. Good luck! I don’t know what’s going on. …

[Bild] maiki: if I told Discourse to accept “localhost”, it will look for it at localhost, which is the Discourse server. I see your reasoning. That’s when it becomes interesting to know what it is actually looking at when it determines access and whether or not it should spit out this error …

Surely someone must know whether or not it should be possible to embed comments from domain forum.foo.com from a localhost development website? I don’t see anything that says it shouldn’t work (by allowing hosts), but since it doesn’t it’s rather unclear.

"Fehler beim Einbetten" Kommentare

Unterstützung

maiki (maiki) 11. Mai 2020 um 19:56 2

Du solltest möglicherweise topicID verwenden, wie unter Embed Discourse comments on another website via Javascript erwähnt.

Es würde mich nicht wundern, wenn „localhost

Thema		Antworten	Aufrufe
Cannot get embedding to work Support	11	2595	31. August 2021
Comments not embedding, 500 Error Feature pr-welcome	15	2003	3. Oktober 2017
Discourse embed blocked on "Loading Discussion..." Support embedding	6	2611	13. Oktober 2015
Embedding comments issue Support	5	2307	26. Juni 2015
Discourse embed: inconsistent errors Support	12	2042	6. November 2017

"Fehler beim Einbetten" Kommentare

Verwandte Themen