WA Kit causing CORS errors on FA Pro elements #2031
Unanswered
russ-sdg
asked this question in
Ask For Help
Replies: 1 comment
-
|
To clarify "I don't reference these in my code, but they are in the kit that I'm linking." means that my code doesn't reference these FA Pro elements, but the js kit provided by Web Awesome that gives me access to my WA Pro features references these FA Pro elements. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm Pro in WebAwesome, but not FontAwesome.
I want to use Pages (a Pro feature) and created a WA project. When I include the script for the WA kit in the head of my pages, I start getting CORS errors that crash my project.
The CORS errors reference FontAwesome pro elements (e.g. sharp-duotone). I don't reference these in my code, but they are in the kit that I'm linking.
I've tried doing it with a FontAwesome kit (selecting only Free icons) and leaving the FontAwesome kit field blank.
I've tried doing it with specifying a domain and leaving the domain field blank (so it's open for any site).
No matter how I do it, I get the same errors.
Here's my kit code: <script src="https://kit.webawesome.com/d9de6fdbad8844e2.js" crossorigin="anonymous"></script>
How can I get a WA kit that doesn't try to include Pro FA elements?
Beta Was this translation helpful? Give feedback.
All reactions