I haven't tried publishing to a network; I like to review a published project before uploading it, anyway.
It wouldn't surprise me if bad things were to happen, though, as Storyline has other problems with doing things on a network. Loading and editing Storyline files directly from a network drive is frowned upon because there's a known issue with content disappearing. My own experience with it is that I'll save, only to discover that the .story file size has shrunk dramatically, and when I next load the file, none of the audio or pictures will load.
Working from a network drive can lead to files becoming corrupted. I used to use Captivate and it was recommended that we save to a local drive rather than a network. You can back up your files on a network drive but don't work from the network drive.
It's mainly about permissions (SL treats you as Admin but, the network destination most likely does not) and it's also about the resources needed to publish which they all sit in your hosting PC. Best practice would be to ZIP the output, transfer it and extract it at the new location. I do it in SharePoint libraries and never have issues.
Can anyone tell me if saving on the network is still a problem? I experienced that years ago with Articulate Presenter but now have Storyline 3. Things any better?
Yes, we still recommend working on local project files and publishing to a local drive for the best results. If you need to store or back up your content to a network/shared drive you can do so once you have saved and closed the file on your local drive.
9 Replies
I haven't tried publishing to a network; I like to review a published project before uploading it, anyway.
It wouldn't surprise me if bad things were to happen, though, as Storyline has other problems with doing things on a network. Loading and editing Storyline files directly from a network drive is frowned upon because there's a known issue with content disappearing. My own experience with it is that I'll save, only to discover that the .story file size has shrunk dramatically, and when I next load the file, none of the audio or pictures will load.
Working from a network drive can lead to files becoming corrupted. I used to use Captivate and it was recommended that we save to a local drive rather than a network. You can back up your files on a network drive but don't work from the network drive.
Hi Sharron,
This is documented here in regards to working from and publishing to a local drive.
Hope that helps.
It's mainly about permissions (SL treats you as Admin but, the network destination most likely does not) and it's also about the resources needed to publish which they all sit in your hosting PC. Best practice would be to ZIP the output, transfer it and extract it at the new location. I do it in SharePoint libraries and never have issues.
Thanks Alexander for sharing that method here.
I've used other authoring programs that had similar problems (i.e. corrupted files when saving).
The best resolution was to save to a different file name each time.
Thanks for sharing your solution Allen.
Can anyone tell me if saving on the network is still a problem? I experienced that years ago with Articulate Presenter but now have Storyline 3. Things any better?
Hi Ben,
Yes, we still recommend working on local project files and publishing to a local drive for the best results. If you need to store or back up your content to a network/shared drive you can do so once you have saved and closed the file on your local drive.
This discussion is closed. You can start a new discussion or contact Articulate Support.