cjk77
(Chris Klugewicz)
April 25, 2020, 11:48pm
1
I’m trying to make use of a special font in one of my theme components. I’ve followed the instructions in this post:
Themes and theme components allow you to handle uploaded assets such as images and fonts. You can control what assets your theme accepts using the site setting: theme authorized extensions
Including assets in themes and components
For remote themes
Remote themes include:
Themes and components installed from the Popular list of themes
Themes and components installed using the From a git repository method
To upload assets to a remote theme or theme component, see Create and share a font them…
Here’s the CSS in my component:
@font-face {
font-family: 'northwood';
font-style: regular;
src: url($northwoodhigh) format('woff2');
}
.category-list tbody .category h3 a[href] {
color: #ccc;
font-family: 'northwood', cursive;
font-size: 135%;
word-spacing: 3px;
}
I’ve added my Cloudfront URL to the CORS setting like so:
But it doesn’t work – unfortunately, I get a “Cross-origin request blocked” error in the console when I load a page with that CSS:
(Sorry for the very smol image.) Does anyone have any advice? I’m stuck.
Do you have the DISCOURSE_ENABLE_CORS
in your app.yml
as suggests the description?
1 Like
cjk77
(Chris Klugewicz)
April 26, 2020, 11:30am
4
Not sure – is there a way to check? (I’m on a hosted instance of Discourse, so I can’t look at the config files directly.)
Edit: I emailed our hosting provider to see if that’s the problem.
cjk77
(Chris Klugewicz)
April 26, 2020, 3:33pm
5
Update: my hosting provider confirms that DISCOURSE_ENABLE_CORS
is set to TRUE
.
So, I’m still baffled.
Johani
(Joe)
April 28, 2020, 1:51am
7
I just tried this, just like you described, on a site with a CDN setup and it worked. So, I think this might be limited to your site.
I think the DISCOURSE_ENABLE_CORS
setting is the inverse of what you want. Adding domains to that setting will allow requests from those domains access to your Discourse domain, not the other way around.
What you want is to allow requests from your Discourse domain to get access to the file on your CDN. I think your CDN is blocking those requests. You can confirm that by running something like this in a terminal window, after you change the values of course.
curl -H "origin: YOUR_SITE_URL" -v "PATH_TO_THE_FONT_ON_YOUR_CDN"
If everything is setup correctly, you should see something like this in the response headers
Access-Control-Allow-Origin: *
2 Likes