Hello, so this is quite a specific bug, but his impact may go far beyond this specific case, and so i’ve got a question about it. (Also, i apologize for my english, i’m french, so not a native speaker at all…) But first, let me explain the context. I’ve been using Discourse for a while for a fre…

[Bild] OsaAjani: window.EmberENV.EXTEND_PROTOTYPES = {String: true, Array: false}; This is not supported at the moment, we rely on the extensions. Perhaps in a future version we will not. @eviltrout can provide more context. I am not sure what to do here, but I think we should have some work…

How are you adding the scripts needed for Quantcast? Are you adding them via a script tag with a src (external) like so <script src="foo"></script> Or are you adding them inline like so? <script> alert("Hello World!"); </script>

Hi, thanks for your responses. @sam I opened a ticket with quantcast the day i’ve created this topics and they responded to me today, apparently they are taking a look at it right know, hopefully they will find a fix for it. I do think this is a quite easy fix for them as the button “accept select…

I can’t see us removing the array prototypes safely any time soon. They’ve been quite harmless over the years and add a lot of convenience. Maybe you could reach out to Quantcast to get a version of the scripts that don’t rely on array prototypes?

Hey everybody, i’ve got some new informations for you and i’ve find a solution to this problem. So, today i’ve been diging again on this bug and i think i have found more infos. By looking at the file cmp2ui-fr.js of quantcast, i’ve been able to find where the bug happen, it’s in this function (w…

Many thanks @OsaAjani for being onto this. We have the exact same problem with Quantcast choice on our Discourse forum and are stuck with their version 12 (which was the last version that does not throw the error). The latest version is 23 and we would very much like to use the latest one. Looking…

Hello @Terrapop i’m happy if this subject can help you. For now i’ve got absolutly no feedback on the issue that i opened on ember.js repo ( [Bug] Property "_super" is enumerable on Array, creating conflicts with external libs (ex : Quantcast Choice RGPD) · Issue #19289 · emberjs/ember.js · GitHub ). …

We added the line before loading choice.js. This seems to work fine, too. For the other solution: We don’t have a reverse proxy in front of our Discourse, so not sure how to create the fix_ember.js file in a proper way. Is that even possible within the Docker? Any suggestion?

Well, if you can load it before choice.js it’s even better !

Yep, works. We can’t thank you enough, we scratched our heads for days about this as we could not find the problem. We had 20 emails back and forth with Quantcast, and they could not locate the problem either.

Konflikt mit Quantcast RGPD-Lösung "choice" und ember.js

Entwickler

Terrapop 15. Dezember 2020 um 17:52 13

Wird gemacht. Guter Punkt.

Thema		Antworten	Aufrufe
Error: Can't access property "registerAsyncHelper" Support	2	939	23. März 2022
Preparing for Discourse's upgrade to Ember 5 Announcements	53	8696	8. April 2024
控制台报错，site.mobileView/site.desktopView功能异常 Support	4	186	21. Januar 2026
New installs will default to Ember CLI builds in Production Announcements ember	36	4313	17. Juni 2022
TypeError: Cannot read property 'id' of undefined Support	16	5492	29. November 2018

Konflikt mit Quantcast RGPD-Lösung "choice" und ember.js

Verwandte Themen