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.

33 Replies
Dayn Wilkins

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

 

 

 

Ashley Terwilliger

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. 

Ashley Terwilliger

Hi all,

I wanted to provide an update here, as Storyline 2 Update 11 was just released, and included a number of fixes which you can see in the release notes available here. The item you all may be particularly interested in is how it fixed an issue where

  • Fixed issue where file attachments wouldn't be saved in the Storyline project file prior to publishing

You can download the latest update here, and after downloading and installing the latest update you’ll want to republish any existing content to ensure that the updates and fixes are applied.

Let us know if you have any questions, either here or by reaching out to our Support Engineers directly.