Forum Discussion
Moving a story file
I created the majority of a module using the 30-day trial version of Storyline, and I have five days left on the trial. My client has since purchased Storyline and sent it to me on a laptop that they would like me to use to develop the rest of the course.
I tried moving the course to the new computer by copying the STORY file up to dropbox and then downloading it. When I opened it on the new computer, there were quite a few problems with the file, especially with the fonts. I had created the course using some purchased templates that I then modified to create the look and feel we wanted, and in many cases the font sizes and other characteristics seemed to have reverted to the original formatting.
I'm guessing it's possible that some of this may have been an issue of not moving the templates along with the STORY file, but are there other issues that come when files get moved. Is there some step for moving them that I missed? I can't find anything when I search the Articulate site using a "move story files" search.
In Studio, there was some way of packaging the files before sending them to someone that got around the strange things that happened when transferring files. I don't remember if that was something from Articulate or a plug-in I found.
Thanks for any help! I'm in crunch mode to deliver this first module in a few days and having trouble with the computer I'm working on, so I'd really like to be able to move this project to the new computer ASAP, but I don't want to have to reformat all of the content on 40+ pages.
I was working locally in the My Articulate Projects folder. It's Windows 7 in Parallels on a Mac, but it's a virtual machine, and I can't imagine that Articulate thinks it's anything other than a regular Windows 7 computer.
Hi Alex,
You could look at uploading it to the shared drive after the fact, following the collaboration article here.
If you were linking to a document as a web object or URL on your server, that may be a better way to ensure the link stays active as it's not imported the file but referring to an external site.
Hi Ashley
Has the issue with links to files (PDFs) been resolved? I'm using SL2 Update 10 and links to files (doc files in my case) still seem to be broken if the external file isn't there when I publish. Even if I've published beforehand it while it was there. The file doesn't appear in the external_files folder in the published output.
I have a project with several modules, with numerous linked files, that I need to hand over to a client soon (.story files). It will be very messy if we also have to pass over all the linked files and they then have to remake the links at their end.
Thanks.
Hi there, Dayn. I'm sorry you're feeling hung up on this issue as well. I can assure you that our QA team is investigating this behavior, so please stay tuned for an update. We'll post a comment in this thread as soon as we can.
The workaround that we've identified for the resources not properly attaching is to attach the resource and then publish the file. The resource file should then be properly saved in the .story file. It sounds like you are not having success, though.
When you attach your resources and then publish your file, are you finding that those resources are still not being preserved in your .story file? Is this happening in every file? Also, are you working on your local C: drive, including your resources? We'd be happy to help you test it out if you'd like to submit your files to us.
(edited to add a missing word)
Hi Crystal
Just done a bit more testing and this is what I've found...
If I link to a file from a trigger on an object in the storyline content, then the file does not get added to the Storyline project after publishing. So if I delete or rename the file, or move the .story file to another PC, the link is broken.
If I add the file as a Resource in the Player settings, then the file does get added to the .story file after publishing. I can then (presumably) link to the published resource file from an object using a Jump to file trigger with the URL "story_content/external_files/MyFile.doc" (as in the past).
I have to say though that we're now on Update 10 and this has been broken since Update 4, so - most of SL2's working life so far. Can we expect a fix soon?
Thanks
Dayn, I also came across this nice explanation regarding the Resources attachment situation which you might find useful as well. Apologies if it is redundant.
What would be very helpful is if you could link to a pdf or external file with a RELATIVE path (instead of it defaulting to C;\mydrive\myproject...), That way we could hand over the story file with the pdfs inside of a directory and the links would be preserved. Hope we can do this soon, clients hire us to start projects and then want the files themselves so they can finish it in-house. Right now they have to re-link all the external files when they get the project, even if they are attached as a resource.
Hi A,
It's not a current set up, but again you're welcome to share your thoughts on this directly in the form a feature request.
okay, thank you!
Hi Dayn,
Thanks for clarifying which way is working for you and which way isn't. You'll also see we have steps documented here for linking to the file in the course resources set up. In addition to that, you asked about a timeframe in regards to the fix and unfortunately we're not able to offer a timeline or a date in regards to this fix, but once we do have additional information to share we'll be able to update this discussion with that information.
OK thanks Ashley.
No problem Dayn and just an FYI that responding via email includes your signature here so you're welcome to edit the post and remove that information if you wish.
Done. Thanks Ashley!
That's good news. Thanks for the heads up!
I know this thread is super old. We are experiencing the same issues. Our vendors have the project opening a PDF document uploaded from their G drive. The story file also has audio and images inside the story project to. The issue we are having is when we download the storyline 360 project and open on our desktop and make a simple change, then re-publish, the PDF no longer shows. It sounds like the PDF should be added to the project, but seems to be lost during the re-publishing stage. Any ideas as to why this is occurring? Our vendor is using Storyline 360.
