Hey there, Marije. Have you tried testing your course in SCORM Cloud? We'd be interested to see if it behaves the same way, especially since you can see those files in the published output folder.
Do you get an error message of some sort? Please be sure you are not still viewing the content locally as that will cause issue. View the content as your learner would within the LMS.
Thanks Marije, that's helpful. So, were the pdfs local to your PC when you attached them - as working from your local drive exclusively is recommended or is the filename long? I've seen these things cause issue.
The PDF's are saved on a drive that is not accesible by all employees. We have made sure that the file name is short. Yet the file location is long. This is an example of a file location.
S:\Staven\Contact Center\Support\Opleidingen\Flipping the Classroom\Story Boards en materiaal\Pensioen\Verschillende documenten\Jaaropgave pensioen
Furthermore, I have tested publishing the e-learning as a CD and saving the published file on an USB stick. When opening the Launch_story file, the E-learning opens and the PDF's are accesible without any error message.
I've encountered the same issue with Storyline 1.0. A previous version of the online course worked fine. But none of the links in my latest version function now.
Be sure the file paths to your projects and published output are well under the 260-character limit imposed by Microsoft Windows. (Publishing adds characters to the file path you selected. If it exceeds 260 characters, your published output will be incomplete.)
Avoid using special characters, accents, or symbols in your file paths and file names. Learn more about naming conventions in this Microsoft article.
11 Replies
Hey there, Marije. Have you tried testing your course in SCORM Cloud? We'd be interested to see if it behaves the same way, especially since you can see those files in the published output folder.
Dear Crystal,
Our company policy/security doesnt support any Cloud based websites. Hence this is the reason we choose to upload via the document added.
Is there any solution?
Hi Marije!
Do you get an error message of some sort? Please be sure you are not still viewing the content locally as that will cause issue. View the content as your learner would within the LMS.
E-learnings are uploaded in Scorm 2004. View the attachment for an example. I made sure that the content was viewed from different laptop than my own.
Thanks Marije, that's helpful. So, were the pdfs local to your PC when you attached them - as working from your local drive exclusively is recommended or is the filename long? I've seen these things cause issue.
The PDF's are saved on a drive that is not accesible by all employees. We have made sure that the file name is short. Yet the file location is long. This is an example of a file location.
S:\Staven\Contact Center\Support\Opleidingen\Flipping the Classroom\Story Boards en materiaal\Pensioen\Verschillende documenten\Jaaropgave pensioen
Furthermore, I have tested publishing the e-learning as a CD and saving the published file on an USB stick. When opening the Launch_story file, the E-learning opens and the PDF's are accesible without any error message.
Any luck on this yet?
I've encountered the same issue with Storyline 1.0. A previous version of the online course worked fine. But none of the links in my latest version function now.
Hi Marije!
Have you tried to shorten the file path?
Be sure the file paths to your projects and published output are well under the 260-character limit imposed by Microsoft Windows. (Publishing adds characters to the file path you selected. If it exceeds 260 characters, your published output will be incomplete.)
Avoid using special characters, accents, or symbols in your file paths and file names. Learn more about naming conventions in this Microsoft article.
Hi K!
Do you have a .story file you'd like us to take a look at?
I published my course to a regular file server. Our IT tech just copied it to a web server and it appears to be working now.
Ah, very good K! Thanks for popping in with an update.
This discussion is closed. You can start a new discussion or contact Articulate Support.