I have built a short course and I created a trigger to Jump to URL/File. I want to jump to a file I have uploaded in my Resources - ElectionStatusAid.pdf.
I have put in the Jump to URL/File as - story_content/external_files/ElectionStatusAid.pdf
I can post my .story file if that would help, but can anyone see anything obvious I'm doing wrong?
The slide 1.6 has a trigger linking that green document button to two different pdf's - you'll need to have two buttons one for each doc unless you combine the pdf's into one document -does that make sense
I placed the pdf on my desktop, opened the .story file, added the link to the pdf on slide 1.6. Published the file to web and played it - no issue, when I click the document icon the pdf opens.
Make sure you have the pdf stored locally when you are linking to it. Then when you publish it will be bundled up with all the files into the external_content folder.
We store all of our storyline files on our internal windows server to enable multiple people to access files. Our attachments are saved here too, however when publishing, the attachments don't actually get copied to the external files folder. Now I know you mentioned in the above that the files have to be local, however this makes it difficult for organisations working with bigger teams.
For example our storyline file is located, opened and saved here, no need to have it located on your desktop:
//SERVERNAME/client files/Storyline file.story
Any attachments we link to:
//SERVERNAME/client files/attachments/my.pdf
Do you know if this will ever be supported? As you can imagine this creates a nightmare for us working with many developers as we need to drop files in on publish and it's not always known if a project has attachements.
As Wendy stated, we do recommend working and publishing files from a local source. This would include any resource pdf files that you attach to the file. If you need to work from a network environment, we would suggest to follow the steps here.
8 Replies
Hi valerie
do you want to post the .story file and the pdf
Hi Valerie
The slide 1.6 has a trigger linking that green document button to two different pdf's - you'll need to have two buttons one for each doc unless you combine the pdf's into one document -does that make sense
Sorry - that was the one I was using to try and get it to work.
Here is the original one with only one link - which I still cannot get to work.
thanks!
Hi Valerie
I placed the pdf on my desktop, opened the .story file, added the link to the pdf on slide 1.6. Published the file to web and played it - no issue, when I click the document icon the pdf opens.
Make sure you have the pdf stored locally when you are linking to it. Then when you publish it will be bundled up with all the files into the external_content folder.
Here is the zip output
Hi Wendy,
We store all of our storyline files on our internal windows server to enable multiple people to access files. Our attachments are saved here too, however when publishing, the attachments don't actually get copied to the external files folder. Now I know you mentioned in the above that the files have to be local, however this makes it difficult for organisations working with bigger teams.
For example our storyline file is located, opened and saved here, no need to have it located on your desktop:
//SERVERNAME/client files/Storyline file.story
Any attachments we link to:
//SERVERNAME/client files/attachments/my.pdf
Do you know if this will ever be supported? As you can imagine this creates a nightmare for us working with many developers as we need to drop files in on publish and it's not always known if a project has attachements.
Regards
Alan
Hi Alan
I know from experience that I have had issues with assets that are not located locally when using Storyline.
Read this support link about how you should be working locally to avoid erratic unexpected behaviour with Storyline files.
http://www.articulate.com/support/storyline-2/create-edit-and-publish-articulate-storyline-courses-on-your-local-hard-drive
Don't shoot the messenger...lol
Hello Alan,
As Wendy stated, we do recommend working and publishing files from a local source. This would include any resource pdf files that you attach to the file. If you need to work from a network environment, we would suggest to follow the steps here.
This discussion is closed. You can start a new discussion or contact Articulate Support.