I have text boxes that will not retain formatting changes. I have changed the text wrap and color on several boxes and saved my changes. I have found that sometimes the text box will revert to it's original formatting even when I haven't closed the file. It will also do it if I close and reopen the file. It's as if the "save" has no effect on the text box itself.
We are happy to troubleshoot this issue with you! Are you finding this is happening in multiple projects or just this specific one you are working on? Also, are you saving the project to a network drive?
We recommend always saving and publishing Storyline projects on your local hard drive (typically your C: drive). Working on a network drive or an external USB drive can cause erratic behavior due to latency. For example, it could cause file corruption or prevent you from saving changes.
In this instance, it's one specific file. He is working on his local drive and even just saving there and reopening seconds later, the changes have disappeared.
Yes, we are working on local drives. We work off of our local drives, but the files are then copied up to our network so that other team members have access to the files. Are you saying that we can't store files on a network drive without the risk of corrupting them? I just had another team member tell me that the file she's been working on is now corrupt and she has to recreate the file from scratch. Is this a known issue with Storyline? How can we work around this as we are working on a multi-file HUGE project and it has to be worked on by multiple team members so the files cannot only be store on a local drive.
Thanks for confirming your team is familiar with the recommended workflow. From here, I'd like you to work directly with a support engineer so we can investigate further. I created a support case on your behalf, so you'll hear from us via email soon!
5 Replies
Hi Kristin!
We are happy to troubleshoot this issue with you! Are you finding this is happening in multiple projects or just this specific one you are working on? Also, are you saving the project to a network drive?
We recommend always saving and publishing Storyline projects on your local hard drive (typically your C: drive). Working on a network drive or an external USB drive can cause erratic behavior due to latency. For example, it could cause file corruption or prevent you from saving changes.
In this instance, it's one specific file. He is working on his local drive and even just saving there and reopening seconds later, the changes have disappeared.
Yes, we are working on local drives. We work off of our local drives, but the files are then copied up to our network so that other team members have access to the files. Are you saying that we can't store files on a network drive without the risk of corrupting them? I just had another team member tell me that the file she's been working on is now corrupt and she has to recreate the file from scratch. Is this a known issue with Storyline? How can we work around this as we are working on a multi-file HUGE project and it has to be worked on by multiple team members so the files cannot only be store on a local drive.
Hi Kristin,
We do have a recommended workflow for collaboration:
Storyline: Recommended Workflow for Collaborative Network Environments
That’s the process that we are currently using. Our team never actively works on our network.
Hey Kristin!
Thanks for confirming your team is familiar with the recommended workflow. From here, I'd like you to work directly with a support engineer so we can investigate further. I created a support case on your behalf, so you'll hear from us via email soon!
This post was removed by the author