After doing a
launcher app rebuild this morning to get onto the latest Discourse, I’ve run into issues with loading some customized site assets that worked prior to the upgrade: self-hosted
@fontface assets, and, weirdly enough, my site’s favicon.
I’d created a directory at
/var/discourse/shared/uploads/default/customizations to hold this stuff, along with the site’s big and small header images. Looks like this:
As of this morning, most, but not all, of the things in that directory are showing 404. For example, in this screenshot, we’ve got the file
d-logo-wide-copse.png, which is the site header image, and it’s definitely being loaded. The
woff files aren’t:
I can also successfully grab the site headers out of that directory with curl, while the other files (including the favicon!) return Discourse’s 404 error.
As a workaround, I tried uploading the favicon to a temporary topic in Staff, and that appeared to work; I can do this for the
@fontface files, but man, that’s an ugly, ugly, ugly ass workaround. Do you guys have any insight into why the neat and tidy custom location is suddenly puking?
(To forestall a response I’ve seen elsewhere, no, using Google web fonts or another offsite font-host doesn’t give me the flexibility I want—been there, done it, abandoned it.)