Working on rebranding a portal/community/experience login page. The designers, being non-Salesforce folk, have a CSS font-face tag in there that references the font files and I've got them in a static resource now (zipped, no subfolders, resource called fonts
The problem is that I can't seem to use the static resources because they sit on the other side of the auth mechanism, therefore they get redirected to the login page, the HTML gets served back into where it's expecting a font and of course that breaks.
I've tried a couple of approaches so far
url(({!URLFOR($Resource.fonts,'/franklingothicurw-boo.woff')})
which gives a 404 not found
and
url(/esg/s/sfsites/c/resource/fonts/franklingothicurw-boo.woff)
which redirects to the login page and gives OTS parsing error: invalid sfntVersion: 218774561
Is there a way to reference the fonts correctly in a CSS font-face
tag prior to site authentication?
If it makes a difference, these are old style pages, using Force.com/Visualforce tech. No Lightning here I'm afraid
fonts/font...
like thisurl(({!URLFOR($Resource.fonts,'fonts/franklingothicurw-boo.woff')})
. The relative path must include full hierarchy of sub-folder structure and not just the.woff
file only.