No matter what type of font I use (system, custom, Articulate, etc.) when I publish the course to view for web only, it replaces the fonts I choose with Times New Roman.
I built the course in Chrome on the PC side of my iMac (split using Parallels). It doesn't replace the font when I publish to Review. I've viewed it in Chrome, Safari, and IE and it shows up with TNR instead of the fonts I chose every time.
When I publish a SCORM file and put it on the LMS, it has the correct fonts in it. So the problem is just when published for web.
How can I make sure it keeps the fonts I selected when published to the web?
So I just tried publishing this on a Mac instead of a PC, to avoid the problem with Windows 10, but it still replaced my font with TNR. Am I missing something from that thread? Do I need to create it from scratch on a Mac instead of just publish from a Mac to avoid the issue? Or that other thread said they were fixing it on each individual computer. Do I need to get with someone at Articulate so they can fix it on my specific computer?
Are you uploading this to your website or testing it locally? Also, when you view the output, is it all browsers that display the change in font?
If you'd like to share a copy of your Rise course with our Support Engineers we can give it a test too. Reach out here and they'll walk you through some next steps.
Thanks for your response. I was publishing for web and uploading to our server and then testing through multiple browsers, all of which showed the font change.
I'll reach out to the support engineers. Thanks for recommending that!
Was this issue resolved? I'm having the exact same problem - all fonts set to Lato, but changing to TNR when I publish. Course developed using Chrome 65.0.3325.181 on Windows 10
I'm having the same problem - Rise course published for the web and uploaded to a web server. In IE, the fonts show up as Times New Roman instead of my chosen fonts, Lato and Raleway. In Chrome, the fonts are fine.
What's the solution?
* Update: Tested on another machine. Times New Roman appearing in Chrome on that machine. The boss is not pleased.
Are you able to share a link to the course hosted in your server/LMS so that we could also test it? If you have the Rise export zipped folder, it would be helpful to have that too. You can upload here using the Add Attachment button at the bottom of the forum discussion reply window.
Thanks for checking in. I can't get you access to the course on the web server because it's inside our firewall. But attached is just one of the courses where we're seeing the issue.
UPDATE: I submitted a case for this to Articulate support and got this response:
"I can't replicate the issue when I uploaded the exported files to our web server.
Since the issue does not occur on your LMS and our web server, please contact your web administrator. They know best how to solve server specific issues like this."
Unfortunately, the tech support on our end can't find any reason this would be happening either, so that's not much help. If anyone does know of any way their server would be changing fonts only on Articulate Rise products, that information would be very helpful.
Rise content depends on .woff (Web Open Font Format) files to display fonts in Rise, and it's possible that your web server hasn't been configured to allow the download of .woff files.
If your web server is running IIS, you may need to add the .woff MIME type in IIS manager to serve this file type:
Open IIS Manager (Start >> Run >> type inetmgr, then hit enter).
Select the root node from the connections pane. Double-click MIME Types from the features pane.
Click on Add link in the Actions pane. This will open up a dialog box. Enter .woff as the file extension, specify application/font-woff as the corresponding MIME type, and click the OK button.
That's really interesting. On mine, it replaces the font no matter what browser I view it with.
Our tech support still hasn't been able to get this fixed using the MIME Type change, but they're going to give it another shot. Fingers crossed it works this time.
If you're able to share the URL to your published Rise output on your Web Server, we might be able to diagnose the root cause from our end. ...and if you can't share the URL publicly, we'd be happy to have you send it privately.
Thanks Justin! This is what our tech support guy said:
I did install the correct .woff download to the IIS manager on the server. If there's anything Articulate support staff can provide for us to implement to the IIS manager then we can go from there. Let me know if they provide any additional steps needed to take and we can help from there.
So if you have any further advice, it would be very much appreciated. I'll send the URL privately.
Ken, here's what I see in the Chrome DevTools Console when I launch the URL you provided:
Your web server is reporting a 404 error for all of the following files:
Lato-Bold.woff
Lato-Black.woff
Merriweather-Regular.woff
2LWC8d1tdj1ij7Hk-liberationsans-bold-webfont.woff
Lato-Regular.woff
This generally means that the files are not present on the web server, but it could mean that the web server is misconfigured in other ways.
I'd recommend double-checking the folder you exported from Rise, to be 100% sure that those .WOFF files are present inside the \lib\fonts\ subfolder. If they are there, you'll want to ask your tech support person why the web server is saying that they are missing from the server.
Please let us know if there is anything else we can do to help.
Thanks Justin. I checked that lib\fonts folder and those fonts are definitely in there on the server. I sent your response above to our tech support team and let them know the font files are there. Hopefully they'll be able to zero in on the problem.
Okay, we got it working. Turned out, because GoDaddy hosts our server, we had to add some code to the webconfig file in the server's root directory. After the opening <system.webServer> tag in that file, I added this:
29 Replies
It maybe your server does have the mime type for web fonts enabled.
Hi Phil,
Thanks for the reply. I don't want to sound like a dummy, but what is a mime type and how can I get it enabled for web fonts?
Thanks!
Hi Ken,
Perhaps this reply from a fellow community member will get you headed in the right direction.
I think that just might be the help I need. Thanks!
So I just tried publishing this on a Mac instead of a PC, to avoid the problem with Windows 10, but it still replaced my font with TNR. Am I missing something from that thread? Do I need to create it from scratch on a Mac instead of just publish from a Mac to avoid the issue? Or that other thread said they were fixing it on each individual computer. Do I need to get with someone at Articulate so they can fix it on my specific computer?
Thanks!
Hi Ken,
Are you uploading this to your website or testing it locally? Also, when you view the output, is it all browsers that display the change in font?
If you'd like to share a copy of your Rise course with our Support Engineers we can give it a test too. Reach out here and they'll walk you through some next steps.
Hi Ashley,
Thanks for your response. I was publishing for web and uploading to our server and then testing through multiple browsers, all of which showed the font change.
I'll reach out to the support engineers. Thanks for recommending that!
Thanks for reaching out Ken. You should be hearing from someone soon.
Was this issue resolved? I'm having the exact same problem - all fonts set to Lato, but changing to TNR when I publish. Course developed using Chrome 65.0.3325.181 on Windows 10
I'm having the same problem - Rise course published for the web and uploaded to a web server. In IE, the fonts show up as Times New Roman instead of my chosen fonts, Lato and Raleway. In Chrome, the fonts are fine.
What's the solution?
* Update: Tested on another machine. Times New Roman appearing in Chrome on that machine. The boss is not pleased.
Hi Brian and Rob,
Are you able to share a link to the course hosted in your server/LMS so that we could also test it? If you have the Rise export zipped folder, it would be helpful to have that too. You can upload here using the Add Attachment button at the bottom of the forum discussion reply window.
Hi Ashley -
Thanks for checking in. I can't get you access to the course on the web server because it's inside our firewall. But attached is just one of the courses where we're seeing the issue.
UPDATE: I submitted a case for this to Articulate support and got this response:
"I can't replicate the issue when I uploaded the exported files to our web server.
Since the issue does not occur on your LMS and our web server, please contact your web administrator. They know best how to solve server specific issues like this."
Unfortunately, the tech support on our end can't find any reason this would be happening either, so that's not much help. If anyone does know of any way their server would be changing fonts only on Articulate Rise products, that information would be very helpful.
Thanks!
Sorry for the trouble, Ken!
Rise content depends on .woff (Web Open Font Format) files to display fonts in Rise, and it's possible that your web server hasn't been configured to allow the download of .woff files.
If your web server is running IIS, you may need to add the .woff MIME type in IIS manager to serve this file type:
Let us know how this works out!
Thanks Justin,
This seems like it will be much more helpful instruction. I'll run this past our tech staff and see if we can fix the problem.
I appreciate your help!
The problem is browser-specific. The fonts are OK using Chrome but not using IE11 or Firefox 56.
Justin, I can't think you enough. The MIME Type change on the server worked perfectly!
So glad to hear it, Brian. Have a great day!
That's really interesting. On mine, it replaces the font no matter what browser I view it with.
Our tech support still hasn't been able to get this fixed using the MIME Type change, but they're going to give it another shot. Fingers crossed it works this time.
That's a stumper, Ken.
If you're able to share the URL to your published Rise output on your Web Server, we might be able to diagnose the root cause from our end. ...and if you can't share the URL publicly, we'd be happy to have you send it privately.
Thanks!
Thanks Justin! This is what our tech support guy said:
I did install the correct .woff download to the IIS manager on the server. If there's anything Articulate support staff can provide for us to implement to the IIS manager then we can go from there. Let me know if they provide any additional steps needed to take and we can help from there.
So if you have any further advice, it would be very much appreciated. I'll send the URL privately.
Thanks!
Thanks, Ken. I see your Case Number 01349717, and I'll be taking a peek at your URL personally.
Have a great day!
Ken, here's what I see in the Chrome DevTools Console when I launch the URL you provided:
Your web server is reporting a 404 error for all of the following files:
This generally means that the files are not present on the web server, but it could mean that the web server is misconfigured in other ways.
I'd recommend double-checking the folder you exported from Rise, to be 100% sure that those .WOFF files are present inside the \lib\fonts\ subfolder. If they are there, you'll want to ask your tech support person why the web server is saying that they are missing from the server.
Please let us know if there is anything else we can do to help.
Thanks Justin. I checked that lib\fonts folder and those fonts are definitely in there on the server. I sent your response above to our tech support team and let them know the font files are there. Hopefully they'll be able to zero in on the problem.
Thanks for your help!
Okay, we got it working. Turned out, because GoDaddy hosts our server, we had to add some code to the webconfig file in the server's root directory. After the opening <system.webServer> tag in that file, I added this:
<staticContent>
<mimeMap fileExtension=".woff" mimeType="application/font-woff" />
</staticContent>
I refreshed the course where I'd been viewing it Safari and, sure enough, it's fixed. Looks like it's working now in other browsers, too.
Thanks again for all your help, Justin!