Forum Discussion
Fonts are wrong on host server
I'm using the HelveticaNeuLT Pro 107 XBLKCn font for my titles and HelveticaNeu MediumCond for text boxes. These work fine in preview and review360 but not on my hosting server. Where does the host get fonts? the output.min.css file is there under html5/data/css. What am I missing?
3 Replies
Hi GeorgeMoureau,
Great question! When a Storyline course is published, the fonts used in the project are packaged into the published output and referenced through the course’s CSS files. In environments like Preview or Review 360, everything needed to render the fonts is already handled.
When a course works in Review 360 but not on a hosting server, it usually points to a server configuration issue rather than a Storyline issue. A couple of common causes are:
- The server not allowing web font files (such as WOFF or WOFF2) to be served correctly
- Missing or incorrect MIME types configured for font files
- Caching issues on the server
Since your fonts display correctly in Review 360, that suggests the publish itself is working as expected. I’d recommend checking with your hosting provider to confirm that WOFF and WOFF2 font types are enabled and being served correctly.
If the issue continues after checking the server configuration, please feel free to reach out to our support team so they can take a closer look and provide more targeted help.
Fonts used are in the output.min.css file
I have had 'wrong font' appear a few times in the past.
Trouble-shooting processes I used, which fortunately resolved the problem quickly.- Clear caches
- Reinstall fonts with a new package - make sure there are no duplicates.
I have never had to do the following for Articulate courses but I have seen it mentioned: Enable/add a MIME type to the hosting server for Web Open Font Format (WOFF) files.
This particular program was a nightmare, to the point I scrapped it and started over. For whatever reason even you tech team could not or would not answer, storyline would not load the css file (output.min.css). It just kept trying to load html5/data/css/null. I want to find out exactly where the css file was included but didn't get an answer. To make matters worse, the server apparently caches java script. I redid a program, short version as a test, and the server would not stream it. It kept streaming to old version and no matter what I tried I kept getting that version. I finally had to create a new folder and upload the new version to that location to get it to work. Finally when publishing, and this is the strangest of the lot, the directories that contain the scripts for the player (html5/lib/scripts and img) were being created as sockets rather than directories. My upload program ignored them, thus scrambling the player. could not get the modern player to work on that program. As I said, I scrapped it, went back to the classic player, and uploaded to a new folder. All is working now.
