When switching a multilanguage website to a language different from default one the path of custom css specified in the font info file are calculated as
/[language]/sites/default/themes/theme-name/...
while the correct path should be
/sites/default/themes/theme-name/...
this results in a broken css file link.
We temporarily solved this by specifying an absolute URL, but it should be an issue when moving sites that are hosted in a subfolder of a domain.

Comments

btmash’s picture

btmash commented
Assigned: Unassigned » btmash

Oh wow, that is really strange. I'll take a look into what is going on.

btmash’s picture

btmash commented

@macaronibros I'm going to try and look into this tonight - for the broken css file links, is it *all* the files that are broken (the render css and the path to your font file if you are using custom fonts)?

btmash’s picture

btmash commented

Ok, I just tried this out right now with the 2 fonts that I include in the project (one is a custom font, the other is a google font) and was able to get to it just fine...would you be able to post the contents of your .fontinfo file (obscure whatever pieces might be sensitive)? I wasn't able to reproduce this in my first attempt.

btmash’s picture

btmash commented
Assigned: btmash » Unassigned
Status: Active » Postponed (maintainer needs more info)

Marking as unassigned and needing more info for now.

btmash’s picture

btmash commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

I tried to reproduce the issue with no luck and since I asked for more information and have not heard back, I am closing the issue. Please give the dev branch a try and let me know if that helps if you are still running into the issue. If you still are, please reopen this issue so I can try to help.

btmash’s picture

btmash commented
Issue summary: View changes

Added more information on how we temporarily fixed the issue.