The pdfs are in the correct location and the hyperlinks are correct. However, when viewing the published output, I can't get any of the pdfs to open. Hyperlinks to a webpage are working as intended.
No, there are no spaces. The path name is not super long but there is no way I can shorten it as that is where I have to save the project files. Everything has to be on the network drive. Although when I zip the folder and import the content into Saba (LMS) learners won't be accessing the network.
I did try putting the pdf in the published output folder. But when I go to open the module in the LMS, the links don't open.
Don't put the pdf in the published folder. In the story, point to it, and let SL take it from there. When you publish, it is packaged and put in the output folder, but if you do it, the links won't work.
Look in the published .zip file, under story_content/external_files. The files should be there after you publish. If they aren't, it's a problem with the links or location during publishing. Depending on the security settings, you could have timing issues pulling them from the network. In that case, I would put a copy of them on the local drive, and point the links to there. (Only during the publishing process, of course.)
If they are there, it's a problem with the LMS. One thing I will note is that if you are using OneDrive somewhere in the process, external_files is a reserved name for it, and you can't store published Storyline output on OneDrive, unless it is zipped. There may be other systems that have the same problem.
If you are using a mac with a virtual machine, you may actually run into trouble publishing locally. I use parallels and have to point to google drive for it to create the external files folder on the published output.
Thanks for sharing, N. I'm curious – Do you have the Shared Profile setting disabled in Parallels? I've had to be careful not to have that channel open between my Mac and Windows environments.
8 Replies
Hi Brittney,
Are there any spaces in the PDF file names? If so, I've experienced issues in LMS previously and have solved the problem by removing the spaces.
Really long path names can cause the same problem.
No, there are no spaces. The path name is not super long but there is no way I can shorten it as that is where I have to save the project files. Everything has to be on the network drive. Although when I zip the folder and import the content into Saba (LMS) learners won't be accessing the network.
I did try putting the pdf in the published output folder. But when I go to open the module in the LMS, the links don't open.
Here is the path, not super long:
\\sso.vsp.sas.com\amd\Training\Training_Projects\USG Program/AEW001.pdf
Don't put the pdf in the published folder. In the story, point to it, and let SL take it from there. When you publish, it is packaged and put in the output folder, but if you do it, the links won't work.
Look in the published .zip file, under story_content/external_files. The files should be there after you publish. If they aren't, it's a problem with the links or location during publishing. Depending on the security settings, you could have timing issues pulling them from the network. In that case, I would put a copy of them on the local drive, and point the links to there. (Only during the publishing process, of course.)
If they are there, it's a problem with the LMS. One thing I will note is that if you are using OneDrive somewhere in the process, external_files is a reserved name for it, and you can't store published Storyline output on OneDrive, unless it is zipped. There may be other systems that have the same problem.
Hi All,
I'm sorry I forgot to update this thread. Walt your suggestion worked!! Putting the files on the local drive and pointing to them there worked for me.
I appreciate your help!
Glad to hear it Brittney! Thanks for popping back in with an update.
If you are using a mac with a virtual machine, you may actually run into trouble publishing locally. I use parallels and have to point to google drive for it to create the external files folder on the published output.
Hope this helps
N
Thanks for sharing, N. I'm curious – Do you have the Shared Profile setting disabled in Parallels? I've had to be careful not to have that channel open between my Mac and Windows environments.
This discussion is closed. You can start a new discussion or contact Articulate Support.