Forum Discussion
External files not being included when publishing
Has anyone else encountered this?
I have a PDF which is accessed via a hyperlink. The file path is correct and the .story file and the .pdf file are on the same hard drive.
When I publish the file the PDF is not automatically copied into the "story_content/external_files" folder. Clicking the hyperlink results in a "file not found" error. However if I manually copy over the PDF, then the link works fine.
The only way to get it to automatically work is to go back into the dialog box for the hyperlink trigger and RE-LINK TO THE EXACT SAME FILE. This is unacceptable.
18 Replies
I have the same issue with files that get worked on by multiple people - I have to make sure that the PDFs are in the same folder (beside the source file) all the time. If they ever get moved the link will break. Currently I am doing that - and the PDFs are NOT getting moved into an external folder, it is being created in the published file - and is empty and in the zip, it doesn't exist. I have tried copying the PDFs and that folder into the zipped file but it won't work. I haven't had this issue before, it's only happening to me today.
Hi Susan,
How are you linking the PDF files into your course? Did you test the method I previously shared to add them to your Resources tab as that will pull them into the .story file that you share with colleagues:
If you're able to insert the file into your Resources tab (vs. directly linking it on the slide) that should keep the file connected to the .story file. If you still need to provide the link on the slide itself, you can use the steps here to do so.
I did not try that - as they don't want a "resources" tab in the course.
I did find out what the issue was however. I am running parallels and somehow my dropbox path was changed, so the PC side (where I have storyline) wasn't able to properly connect and keep the files with it when published. I ONLY Run parallels because of Storyline:(
Can Articulate PLEASE make a MAC version of Storyline?
Susie:)
Sent from Outlook
Hi Susie!
You can actually still use this method, even if you don't include the resource tab in the player. It really is the safest way to ensure that your links don't get broken down the line.
Our team uses Parallels on a Mac also, and we've had lots of success with it! Let us know if you have any more questions about running Storyline on a Mac.
Hi,
I have the solution.
I know this is an old thread, but I don't know if people are still having issues with PDF files or files not appearing in published files.
We had the same issue but after some research and testing worked out the issue and a solution.
We also want to link to PDF files within the content and not via the tab. We use a trigger.
We learnt that linked via a file on a network drive is very unreliable.
We started putting all the files (storyline, PDF etc) on the local drive and publishing. We noticed that the PDF would be missing from the external_files folder.
We tried loads of things - stuff I'm sure you've all tried.
Eventually we realised the problem was the filename length of the PDF or linked file. If we reduced it massively it always worked. I've got one that is about 25 characters at the moment and this works. Anything that is really long doesn't get picked up.
Reduce the filename of your linked file and you should be fine.
Hope this helps
Scott
I know this is an old thread but just wanted to pop in to say that Scott's solution is what worked for me! I shortened the name of the PDF file that was missing from the published output and re-added it to the Resources tab. Now when I publish the project, the file is in the "external_files" folder as expected.
Hello. I wanted to jump in here as well. This issue happens to me periodically as well. And it just happened again. However, the names of my .pdfs are short. But they are still not being included in the folder when I publish. So I have to manually create the subdirectory and add the .pdfs to the SCORM package. Very aggravating.
Mary-Scott,
It's not just the name of the pdf that counts toward having too many characters. it is the whole path. So moving the file up a few directories may solve your problem.
