Hi, I have this same exact error when trying to integrate javascript embedding on our site. Blog Post: Season 3: Balance and Classic Decks - September 2019 Update | Blog - RoyaleAPI Discourse site: https://discuss.royaleapi.com I have looked at the related topics and also Google but I am not en…

[Bild] seeminglee: I’ve updated the URL to only show the embed while I debug this so our visitors won’t see these Are you sure the ?discuss=1 query param isn’t the cause of the issue? Are there any security permissions on your blog category, or is it set to allow the group ‘everyone’ to Crea…

I am certain that it has nothing to do the ?discuss=1 param. I had the same issue without it — it’s just that this is a live site and I don’t want to show a huge error block to our users. But since you’e asked, I have edited the site and instead enable the javascript embed on only one of our very ol…

Not sure if this could be relevant, but I do see some errors in the logs but I’m unsure what it is: [Fri 06 Nov 2020 04:47:14 PM UTC] Domains not changed. [Fri 06 Nov 2020 04:47:14 PM UTC] Skip, Next renewal time is: Mon 04 Jan 2021 08:07:59 AM UTC [Fri 06 Nov 2020 04:47:14 PM UTC] Add '--force' to…

@simon Is this something that you can potentially help me with? Is this expected behavior or being fixed in a future release? We’ve added this forum mostly to enable commenting on our site pages, and if this will not work then we need to look into other solutions. Thanks!

There is an issue that I hadn’t noticed previously in this screenshot: [image] The Path Allowlist is set to /blog/* instead of to /blog/.* (note the addition of the dot character.) Try editing the host entry to change the Path Allowlist to /blog/.* If that doesn’t fix the issue, try /.* Also try…

Yeah my screenshot had the issue but i have since changed it to /blog/.* already since I realized that it’s likely using regex. However, the problem persists.

@simon I have tried all three: /blog/.* /.* (last one is empty) and none of those work. The error I get in console looks more like a CORS issue than anything else. _embed-application-9cef8308c816fc1d83137e63d6c556c6cc2b68fe2b6e5ce16cca6766ba2c0ae4.js:7 Failed to execute 'postMessage' on 'DOMWi…

On the Discourse Embedding settings page, have you set the “Username for topic creation” setting? If it’s not set you’ll get the Failed to execute 'postMessage' on 'DOMWindow' error.

@simon Yes username for topic creation is set to system. I have also tried setting it to my own username and it gives the same error. Of interest, today I have found the following: curl -IXGET https://discuss.royaleapi.com access-control-allow-origin: * access-control-allow-headers: Content-Type,…

@simon I have resolved this issue. In order to solve another issue Unable to generate preview for URLs - #4 by seeminglee — i have enabled HEAD requests on the site, and now all of the discussions showed up, and in turn, threads get automatically generated for my blog posts. This is amazing — I ca…

JavaScript-Einbettung zeigt keine Einbettung an, Konsolenprotokoll zeigt: Fehler beim Ausführen von postMessage auf DOMWindow…

Unterstützung

simon 14. Januar 2021 um 00:22 13

Vielen Dank, dass du dich darum gekümmert hast!

Möglicherweise sollte dies dem Abschnitt „Fehlerbehebung

1 „Gefällt mir“

Thema		Antworten	Aufrufe
Cannot get embedding to work Support	11	2571	31. August 2021
Embedding comments issue Support	5	2287	26. Juni 2015
"Error Embedding" comments Support	16	2301	4. Mai 2022
Embedding Discourse Comments via Javascript over https Support	3	688	1. März 2020
Embedding error Support	13	3983	21. November 2020

JavaScript-Einbettung zeigt keine Einbettung an, Konsolenprotokoll zeigt: Fehler beim Ausführen von postMessage auf DOMWindow…

Verwandte Themen