The Resource Doc Black hole.....
Mar 30, 2016
I needed to post this to see if this happens to anyone else. You are working on a course, you are at the point where you have added resource docs. You then send the file to another person who makes the finishing touches and exports and puts online. When you go to test the online product none of the resource docs or attachments you added are there. We've had this happen over and over again to the point where you are checking the "Storyline output\story_content\external_files" folder after you publish to make sure the files are there. It seems that once the storyline file changes hands to another PC the attachments disappear. It would be nice if the file(s) just stayed with the course as do the audio/video files one may add.
Does this happen to any one else? Is it just me? Does anyone have any pointers to avoid it?
7 Replies
A known bug means that although they are added to the file, on publish storyline looks to the original location of the files. It unfortunately does not fire off a warning if it cannot find any of the files.
In your process it may be better if the final person adds in the files
Thanks for letting me know. Hopefully the can correct that in future releases.
Thanks Phil for sharing with Adam here - and it is something we've reported to our team, so once we have additional information to share in regards to this behavior we'll be certain to update threads such as this one.
Would using a common network location for the resource files work as a work-around for this? We have web objects inserted, but those files are all located on network drives, so we haven't seen a problem.
I have seen that work when everyone is opening the file from the same network and the attachments are housed in the same place. We run into it when people are working from home and passing thing around off the network. The VPN is too slow to expect to continue to work on the Storyline file on a network via the VPN.
It only affects resources Mike, a common location should fix it but even then drives can get mapped differently.
It is a bug that was introduced as early SL2 and SL1 never had it the file was part of the SL file and was alway attached. It has bit me a few times.
Phil, good to hear as we don't use the built-in Resource feature. :)
This discussion is closed. You can start a new discussion or contact Articulate Support.