Can you please first confirm that you are working and publishing your content exclusively to a local drive, as opposed to a network or USB drive? Here are a few other tips:
1. Work on your local drive (your C: drive). Working on a network drive or a USB drive can cause erratic behavior, including file corruption, loss of audio, and other unexpected behavior.
2. You should also make sure the directory path to your project files and your published output is less than 260 characters (for example C:\Articulate).
3. Avoid using special characters, accents or symbols in your file names.
The message you're seeing from SCORM Cloud is a parser warning and it will not impact tracking.
Here's the official message from SCORM Cloud on this:
"When Tin Can content is uploaded, we try to process it for both versions 0.9 and 0.95. What you're seeing should just be in the 'Parser Warnings' section, and the content you've uploaded should still work. We display the message in case the user uploading the content intended to use it with 0.95.
We will continue to support 0.9, and URI fragments in 0.9."
6 Replies
Hi Nicholas,
Can you please first confirm that you are working and publishing your content exclusively to a local drive, as opposed to a network or USB drive? Here are a few other tips:
1. Work on your local drive (your C: drive). Working on a network drive or a USB drive can cause erratic behavior, including file corruption, loss of audio, and other unexpected behavior.
2. You should also make sure the directory path to your project files and your published output is less than 260 characters (for example C:\Articulate).
3. Avoid using special characters, accents or symbols in your file names.
Publish Settings:
Zipped file saved to: C:\Users\nicholas\Desktop\
Thanks, Nicholas. Any chance you'd be able to send us the .story file so we can do some testing on our end?
Case Submitted.
Hi Nicholas,
The message you're seeing from SCORM Cloud is a parser warning and it will not impact tracking.
Here's the official message from SCORM Cloud on this:
"When Tin Can content is uploaded, we try to process it for both versions 0.9 and 0.95. What you're seeing should just be in the 'Parser Warnings' section, and the content you've uploaded should still work. We display the message in case the user uploading the content intended to use it with 0.95.
We will continue to support 0.9, and URI fragments in 0.9."
Thank you for your help. Good to know its not a problem.
This discussion is closed. You can start a new discussion or contact Articulate Support.