In a Support discussion titled “House ads & adspeed” tagged advertising, anon48433008 seeks help integrating AdSpeed ads into Discourse, noting they work on other sites but not here. They share the ad zone code and mention trying to add g.adspeed.net to cors-origins per pfaffman’s suggestion. After updating to an advanced ad script and experimenting with CORS settings, anon48433008 confirms the browser now attempts to load the script — progress, but not success. pfaffman clarifies that CORS origins must include http:// or https://, which anon48433008 tries without success, but notices the console error changes — suggesting the script is now executing. pfaffman acknowledges progress and theorizes the issue may lie in missing query parameters (after the ? in the script URL) needed by the asld.js file to identify the ad owner or zone. The user remains stuck but closer to a solution, with pfaffman offering encouragement and continued troubleshooting.
With adspeed its a zone and you can place different ads in it, on my video site with the same code there are two ads being served, same with blog but no mobile there yet.
First: I have spent most of my morning working on some problems that someone has had with ads and even after I did three very clever things, the problem has at least sort-of only gotten worse.
I’m glad that I thought you’d see the humor in my sarcasm.
Yes! That’s awesome! Now it would appear that the code is executing. I have spent many hours of my life modifying code that was not executing, so you’re really moving along.
So my idea appears to have been necessary, but not sufficient to solving your problem.
I guess maybe that php thing you’re calling spits out the asld.js file that it’s talking about.
Uh. Maybe? It means that somehow that script wants to know something about some owner and something is supposed to tell it and it’s not getting told. That something is probably in the part after the ? in the src= url in your image above.