Hi @EdwinN1337, at the moment the ability to setup CORS is not supported natively. You might try to change the script url to originate from a subdomain on your site, i.e. code.yourdomain.com, where “code” is a cname record setup to point to your code server.
You might try to change the script url to originate from a subdomain on your site, i.e. code.yourdomain.com , where “code” is a cname record setup to point to your code server.
@cyberdave, could you elaborate a bit on this, or perhaps share any resources that explain this in more detail?
I’m having CORS issues trying to import postscribe. I think your solution sounds promising but I’m not sure I understand it fully.
The cname record would essentially be a proxy for the actual javascript library, right? What kind cname record?
Hi @Greg_Condit, thanks for your reply, CORS would need to be enabled at Postscribe to handle cross domain requests, otherwise you can try to setup a cname record for a subdomain of your main domain and point that at the server hosting the postscribe script.
Basically, the postscribe code will not load unless the code originates on the same domain as the page where the script is run.
Setting up a CNAME like “code.yourdomain.com” that points to where the postscribe script is hosted will allow you to use that for pages hosted under yourdomain.com (although you have to test, custom code is not guaranteed to run"
jQuery is loaded automatically for every Webflow site, so in most cases it is not necessary to load it a second time. I hope this helps.