# May 7, 2013 at 10:02 am
I had the same issue with my blog, and my custom fonts weren’t showing. The cause was that my WordPress install was not located in the root folder of my site, and the fact that there was a difference between the WordPress Address (URL) and the Site Address (URL) in the general settings. I fixed it by using the full path to the custom font files, including the http and domain and all that.
Not sure if that’s also what’s happening here of course (though I do believe Chris is also a supporter of not having the WordPress in the root).# May 7, 2013 at 10:38 am
I’m on the case! It’s pretty complicated actually, because of some new nginx caching going on on the site, amongst other things. They SHOULD work from the CDN, but either Firefox started not allowing cross-origin fonts depite the headers, or my headers are wrong. And my headers SEEM to be right, but it’s hard to know because of the nginx stuff. I would just yank them off the CDN, but even that seems to be problematic in W3 Total Cache (not respecting my rejected files list). And I don’t want to turn off the CDN completely because that would be an even worse problem =).
Anyway, quite the cat and mouse chase here. Thanks for all the information. I’ll get it sorted out soon.
You must be logged in to reply to this topic.