Engage interactions corrupted by networked computers

Jun 03, 2015

Hello,

Why do changes made to a presentation on a local drive affect another version of the presentation, albeit with the same file name, on a network drive?

Our experience:

An Articulate presentation was saved on our company network, available to various users to view and edit. Using the recommended workflow for collaborative environments, I saved a copy of the presentation on my local drive and proceeded to change the colour scheme in an Engage interaction. A colleague used the same recommended workflow and saved a copy of the presentation on their local drive and proceeded to modify images in another Engage interaction. By my count there are now three versions of the presentation (with the same file name) - the original on the network drive, a modified version on my local drive, and another modified version on my colleague's local drive. Then, the most unexpected thing happened: the changes that I made showed up on my colleague's copy, and the changes my colleague made showed up on my copy. To make matters worse, the original now had both our changes. This is unexpected and unwanted. We were both working on our local drives and neither one of us had uploaded our versions to the network drive. Now, the original is lost. Has any other users experienced this? Does anyone know why this happens? 

Thanks,
Norman

3 Replies
Ashley Terwilliger-Pollard

Hi Norman, 

I would suspect that someone opened it up while it was on the Network drive at some point, which caused Presenter to update it's reference to that location.  

If I wanted to be sure that any changes I'd made to a file didn't update the networked version what I would do is create a package of the best version I have available to me, copy it to a new location on C:, disconnect from the network, make a change, and verify that the date/time on the .intr file is being changed. Also, verify that if you open the .intr file directly, the changes are present. Once this is verified, I would reconnect to the network and continue working.

The key here is that an unzipped copy of the project should never exist on the network drive--only the packaged zip file as there is no way for our content to reference an .intr file on a network drive that is packaged up and inaccessible.

Let us know if you need anything else. 

This discussion is closed. You can start a new discussion or contact Articulate Support.