Hello there, @zackai! Thank you for reaching out with your topic.
The new video optimization feature in version 1.6.0 of the plugin requires a feature called cross-origin isolation. For this to work, external resources being loaded from a different host need to provide an Access-Control-Allow-Origin header.
If your site loads JavaScript files from a different subdomain, then your CDN needs to provide this Access-Control-Allow-Origin response header for all these assets. Access-Control-Allow-Origin: https://www.yourdomain.com or the less restrictive Access-Control-Allow-Origin: * should work.
Please contact your website administrator or hosting provider to further assistance with setting the header.
As a short-term workaround, you can disable video optimization in the Web Stories settings, which will also disable the cross-origin isolation and the need for these headers.
Thanks.
Thread Starter
zackai
(@zackai)
Thanks, Luckyna.
About setting the header, my original understanding is that it’s caused by that WebStories plugin is trying to load resources from the google server, and hence the cross-origin. But you are saying it’s because my hosting is trying to load javascript from another subdomain? Do I understand it correctly? If so, I will talk to my provider.
As for disabling video optimization, it helps to mitigate the issues. Thanks.
-
This reply was modified 5 years, 1 month ago by
zackai.
Hi @zackai!
But you are saying it’s because my hosting is trying to load javascript from another subdomain? Do I understand it correctly? If so, I will talk to my provider.
Yep, that’s correct. This CORS error occurs when your site is trying to load files from a different domain than your WordPress domain, so your provider will need to help you adjust your CORS settings to make them less restrictive and allow these files to be accessed.
Hope this helps! Let us know if you have any other questions.
@zackai We will mark this as resolved, but please feel free to open a new support topic if you have any questions. Thanks again for your post!
@luckynasan can you explain this a little more? If I have a WordPress website and a Google Cloud Storage bucket that acts as the CDN for all of the images, and these images don’t show up in Web Stories because of the CORS issue, do I need to make a fix in the htaccess file of the WordPress website or a fix in the Google Cloud Storage bucket?
You’ll need to set up CORS on the Google Cloud Storage bucket. Follow the documentation at https://cloud.google.com/storage/docs/cross-origin to learn more about CORS and how to set it up on your bucket.
hi, I saw an error like this:”Access to font at ‘https://mydomainname.com/wp-content/plugins/elementor/assets/lib/font-awesome/webfonts/fa-solid-900.woff2’ from origin ‘http://mydomainname.com’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. ”
What should I do please?
Need plug in or coding please?
Thanks.
-
This reply was modified 4 years, 6 months ago by
anniechoy. Reason: do not want to public my domain name
@anniechoy If you’d like to open a new support topic we’d be happy to assist with your case individually. Thank you!
