Forum Discussion
Duplicate fonts in SCORM export - Articulate Rise 360
I have an issue when exporting a course that uses the same font for both headings and body (see theme fonts.jpg attached).
When loading the SCORM file to the LMS, I received an error (see error.jpg attached). Upon further investigation, I found that the SCORM content actually lists the same WOFF file twice in the same folder, which is why I'm getting the error (see ZIP duplicate.jpg attached).
My question is: Why is the WOFF file listed twice? Because I used the same font for both headings and body? If so, surely there is an error within the SCORM export within Rise. What is the workaround?
Hi Bruce! I see you're using a Custom font. What versions of the font did you upload? Did you upload only the regular version, or did you also include the italic and bold versions?
Headings in Rise are automatically displayed in bold, and if the bold version of your font isn't available in Rise, it may be using the regular version in its place. Please add in the bold version of your font or if you prefer non-bold headings, you can:
- duplicate your font and rename with "bold" in the name
- upload this so you have both the regular and "bold" versionPlease then try exporting this again, and let me know if you have any trouble!
did this work?
Hello, I have the same issue, and the course is perfectly showing poppins heading for headings and regular for body fonts. Can someone please send me the screenshot of how this duplication of font works.
Hi Daya! To clarify, that suggestion is only if you had uploaded the custom font and did not want to include the bold version.
If you want to do this and have the regular version of the WOFF file, you would:
- right-click the file on your desktop or other file location before upload. (this is not done within Rise)
- Copy the file and rename
Hey, I've got the same issue that hopefully has been solved. It is the publishing to SCORM that messes things up.
I've attached all versions of the font (bold, regular, thin etc.).The problem occurs only in the ZIP-file:
- If I open the ZIP-file, I see duplicates of my custom font.
- If I extract the ZIP-file - the duplicates are gone.
- If I re-ZIP the file, they are still gone.
Hopefully this has solved the issue! Although, the problem still lies within Articulate Rise SCORM packaging of course. Looks like a bug to me.
Hi everyone! In today's update for Rise 360, we fixed an issue where custom font files were duplicated in the output.
You can check out the release notes here. Let us know if you see any issues with your course output!I just published a lesson today and I'm still having the issue with the duplicate fonts. I can't upload to an LMS.
Hi Lauren! Thanks for sharing your SCORM file. I tested it in SCORM Cloud, and it is working:
SCORM Cloud is an industry-standard testing engine that's free and supports AICC, SCORM, Tin Can API (xAPI), and cmi5 content.This video tutorial demonstrates how to use SCORM Cloud with Articulate content.You'll also find some helpful LMS-troubleshooting tips here.Since your course works properly in SCORM Cloud but not in your LMS, kindly share the SCORM Cloud findings with your LMS provider to troubleshoot the issue.Now I’m having trouble uploading another file (attached). What do these error messages mean?
Hey all! I had the same issue with a custom font duplicating. I had to unzip, and it asked if I wanted to replace fonts with duplicates, I agreed, I rezipped, and it uploaded fine to Cornerstone. It was a pain of a workaround, but I could meet my deadline.
Hi there, Jolene! This was a bug in an older version of Rise 360, but it should have been fixed. Thanks for letting us know you're running into it again! Would you mind opening a case and attaching the unedited version of your SCORM file? We'd love to take a look and see if we can recreate this problem on our side. Thanks!
All of a sudden I am also getting the duplicate font error message. I've tried Jolene's workaround - thank you! It works but it's waste work. I'm submitting a case.
Hi everyone, we've been trying to replicate this using steps that caused the original problem from the original post's time (2 years ago) and could not get the same duplication in the published output. If you can share some more details as to how these courses with the duplicate fonts in the published output ended up this way that would be really helpful.
If you can work closely with our support team by opening up a case, that would be even better.
