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.
40 Replies
Hi, Rachel.
Thank you for reaching out! I'd like to get some additional information on your vendor's process:
- It sounds like they're adding a PDF file from a network drive to a Storyline 360. We don't recommend working with files on a network drive, as it can cause erratic behavior.
If that's the case, I recommend keeping the PDF file on the local drive when adding it to the .story file.
If this is not your scenario, let me know, and I'm happy to continue troubleshooting!
Hi Maria,
They did add it via their G drive. We tested in internally. We downloaded the file, added a PDF via our c drive on our local machine. I added it to our SharePoint site to have my colleague download, publish, and zip the file. When we added it to our LMS and tried to open the file, it opened a browser window with the correct extension but never opened the PDF. It seems like it is missing the file during the file transfer. Is there another way to add it that would prevent this from happening?
Thanks,Rachel
How is the pdf being attached to the story? Do a search when you get the .story file, before you edit it or publish it, and see if the pdf is coming as part of the .story file.
I suspect it is not, and they need to send it to you separately.
Walt,
I bet you are right. I have requested they send all their project files. I know when I have used Captivate in the past we had to keep all the files in the folder to prevent the possibility of breaking links.
Would that be the case for Storyline 360 too?
I attached a screenshot of how they are adding the file into the project. Is there a better way?Thanks,
Rachel
I can't tell for sure, but looking at the trigger, I am suspicious. Those are not the sort of folder and file name I would expect. I might be wrong, but if they published the project, then went looking for the pdf, I would expect names like this. Drive letters as high as G: are typically network, or removable drives. Of course, neither of those observations is set in stone, and both could be wrong.
What is pretty immutable is that the "open" trigger points to a file on the disk. It is highly unlikely that that file resides at the same exact spot on your disk as it does on mine. I believe you have to publish the project from the same computer where the trigger was created. Get your hands on the file, create the trigger, and publish it. If you send it to a colleague to publish, they need to edit the trigger to make sure it points to the file on their computer before they publish it.
Walt,
That makes sense to me. I appreciate your input.
Best,
Rachel
