I just upgraded a site from Bricks 2.1.4 to 2.3.4. All custom fonts (I use Nexa) are no longer working. They are not being displayed in the editor nor the front end (https://timothywest.com). I instances default the a a fallback font (Helvetica it looks like).
What’s strange is that the font is not loading in the font manager:
…but when I inspect the font variation, they do display:
Hi,
Thanks for your report!
In order to possibly reproduce the issue, we first need to know how to replicate your setup, since your images and custom fonts appear to be served from a subdomain, which can be particularly problematic with fonts because the browser treats them as different sources—in other words, this may be a classic CORS issue—at least that’s what the message in the console suggests.
In theory, you need to tell photos.timothywest.com to allow requests from timothywest.com.
Apache — add to .htaccess on photos.timothywest.com:
<IfModule mod_headers.c>
<FilesMatch "\.(woff|woff2|ttf|otf|eot)$">
Header set Access-Control-Allow-Origin "https://timothywest.com"
</FilesMatch>
</IfModule>
Nginx:
location ~* \.(woff|woff2|ttf|otf|eot)$ {
add_header Access-Control-Allow-Origin "https://timothywest.com";
}
It’s possible that one of the changes within Bricks is causing it not to work as it did before… but as I said, to figure that out, we first need to know how to replicate your setup.
Best regards,
timmse
Thanks for the insight. I now see in the DOM that fonts are trying to be pulled from the photos.timothywest.com subdomain (which is not where they are). This is caused by WP Offload Media…I will investigate further with them. No bug. Cheers