check your file path because there is a limit of 260 characters in file names including directory names (path + file name).
Articulate points out, that your project and your published course should be stored locally.
If you move external files (resources) to a different directory, you have to go to your player settings and you have to change the path to the files for every file which is now located somewhere else.
I have not tried SharePoint yet but I do not think SharePoint is supported by Storyline2 since Articulate recommend only local file storage and denies any network storage.
Alternatively, you can add the .pdf in your resources section of the player. If you are using a custom user interface and would like to link your pdf to a button use a hyperlink and link to the pdf. Remember to change all the "\" to "/" and add the folder containing your pdfs to the exported folder. And example of the pdf hyperlink should look like this in your trigger "resources/mypdfname.pdf
@Jan Thanks for your reply. I think the issue was resolved by shortening the name of the PDF, as you suggested I must have exceeded the 260 characters.
@Dirk, thanks also for your reply. I am using a custom interface with none of the player elements switched on. I noticed that once I shortened the file names that the files did appear in the external files directory of my published project, when digging I found that previously they weren't being included at publish which is obviously where my issues lay.
4 Replies
Hi David,
check your file path because there is a limit of 260 characters in file names including directory names (path + file name).
Articulate points out, that your project and your published course should be stored locally.
If you move external files (resources) to a different directory, you have to go to your player settings and you have to change the path to the files for every file which is now located somewhere else.
I have not tried SharePoint yet but I do not think SharePoint is supported by Storyline2 since Articulate recommend only local file storage and denies any network storage.
Alternatively, you can add the .pdf in your resources section of the player. If you are using a custom user interface and would like to link your pdf to a button use a hyperlink and link to the pdf. Remember to change all the "\" to "/" and add the folder containing your pdfs to the exported folder. And example of the pdf hyperlink should look like this in your trigger "resources/mypdfname.pdf
@Jan Thanks for your reply. I think the issue was resolved by shortening the name of the PDF, as you suggested I must have exceeded the 260 characters.
@Dirk, thanks also for your reply. I am using a custom interface with none of the player elements switched on. I noticed that once I shortened the file names that the files did appear in the external files directory of my published project, when digging I found that previously they weren't being included at publish which is obviously where my issues lay.
Advice from both was much appreciated.
Thanks for sharing your solution with the community David :)
This discussion is closed. You can start a new discussion or contact Articulate Support.