Forum Discussion
Storyline publish file deleted files out of computer folder of same name
I just experienced the same issue. I had 10+ versions of my storyline file plus source documents saved in a local folder. When I published the file it wrote over this folder and I lost all saved files aside from my current storyline file. Brutal. Of course this is the one project where I haven't been backing up my local files to the cloud. Wild that there is no alert when attempting to publish to a folder of the same name.
Hi woowootootoo,
Thanks for sharing what happened. I'm really sorry to hear you lost your project files. I can understand how frustrating that would be, especially after having multiple Storyline file versions and source documents saved in the same folder.
I'd like our Support Engineers to take a closer look at your publishing workflow to better understand what happened and determine whether there are any recovery options available. I've opened a support case for you, and someone from the team will reach out shortly to gather a few additional details.
In the meantime, if you haven't already, I recommend avoiding any further changes to that folder until the team has had a chance to review the situation, as that may help preserve any potential recovery options.
Hi Eric,
Thank you for opening a support case and connecting me with a customer support agent.
It does concern me that this thread documents several users experiencing the same issue over the past three years.
Software should not silently delete unrelated documents, previous file versions, and subfolders without warning. At minimum, Storyline should clearly warn users that publishing will permanently replace the folder's contents.
The risk is compounded by Articulate's recommendation to work and publish locally.
I appreciate support looking into my case, but I hope the team will also address the need for additional safeguards.