I work on a collaborative team with a version control system. Each member downloads the files locally to work on them, and then uploads them to the shared server. Each of us has the same file structure and path to our Storyline projects on our computers.
When I work on a project and create a link to an external file, like a pdf, it appears correctly in the external_files folder when I publish the project. But when my co-worker downloads the project files and publishes, the external_files folder is created but it's empty. The path in the trigger window should be a valid path on both my and my co-worker's computers.
I'm not familiar with what you are describing. Are you working as described below:
When working on an Articulate Storyline project in a collaborative environment with other developers, use this workflow to avoid loss of resources, file corruption, and other erratic behavior.
We've traced our problem to a slight difference in our paths on each computer. Three characters were formatted differently on one of the folder names on our two computers.
Once we aligned our folder names to match exactly we were able to publish correctly from either computer and have the linked files working as they should.
That brings up a more relevant issue and feature request: if Storyline allowed us to use relative paths rather than absolute paths to the connected assets none of this would have happened.
This is important for those of us working in collaborative environments, but could also affect someone working on a single computer.
Suppose you have two folders on your computer: Current Work and Past Work. You build your project and connect external files while in the Current Work folder. Once done with the project it's moved to Past Work. Then if you try publishing, the externally linked files will not be included in the build because the absolute path name has changed.
6 Replies
I should have said we're using Storyline 2. Is it related to this issue:
http://www.articulate.com/support/storyline/file-path-for-jump-to-urlfile-trigger-converts-to-double-slashes
Hi George!
I'm not familiar with what you are describing. Are you working as described below:
When working on an Articulate Storyline project in a collaborative environment with other developers, use this workflow to avoid loss of resources, file corruption, and other erratic behavior.
Leslie,
We've traced our problem to a slight difference in our paths on each computer. Three characters were formatted differently on one of the folder names on our two computers.
Once we aligned our folder names to match exactly we were able to publish correctly from either computer and have the linked files working as they should.
That brings up a more relevant issue and feature request: if Storyline allowed us to use relative paths rather than absolute paths to the connected assets none of this would have happened.
This is important for those of us working in collaborative environments, but could also affect someone working on a single computer.
Suppose you have two folders on your computer: Current Work and Past Work. You build your project and connect external files while in the Current Work folder. Once done with the project it's moved to Past Work. Then if you try publishing, the externally linked files will not be included in the build because the absolute path name has changed.
Thanks for sharing your findings and your thoughts George.
Did you share that feature request with our developers here?
Leslie,
Thanks for the suggestion, I've submitted a feature request with your team.
Thanks so much George.
This post was removed by the author
This discussion is closed. You can start a new discussion or contact Articulate Support.