The case of the disappearing images

Jun 16, 2014

Hello Heroes!

I have more of a detective inquiry than a call out for a hero.  So, Bat signal alight, here's my problem. 

My work partner sends me story files which include whatever images she has found to add.    We've done several projects with no problems but suddenly the file I received show images in the StoryView but when I open the actual slide all I see are empty boxes.  She has tried opening a new story file and copying the contents into it.  We haven't changed our image format so I'm wondering where my images are.

Na Na Na Na Na Na Na Na Help Me!

Jay

4 Replies
Ashley Terwilliger-Pollard

Hi Jay,

When I've seen this in the past, it was the file itself having some level of corruption that allowed for the images on the slides to disappear but were still on the thumbnails in Story view or the slide sorter. Since you're sharing files back and forth, you'll want to confirm that you're following these guidelines for a collaborative work environment and  that you also both work with local files whose file names adhere to the guidelines mentioned here. 

If your colleague is still able to open the file and see the images, I'd have her begin by importing it into a new project as described here and ensuring it's saved and opened from a local drive. 

Ashley Terwilliger-Pollard

Hi AM,

This thread is a bit older - are you using Storyline 1 or Storyline 2? Within Storyline 1 it was something we saw a number of times from other users but not something we could replicate, but so far haven't seen it within Storyline 2. Generally when it was happening with users before it was a sign of corruption within the file, and corruption is notoriously difficult to track down.Common causes are environmental (disk errors, power outages, improper shutdowns), viruses, failed Windows updates, and even file size (i.e., very large files have a higher risk of corrupting).

Consider these preventative measures to protect your project files:
 
1) Save and publish projects on your local hard drive. Working on a network drive or external USB drive can cause erratic behavior due to latency.
 
2) Save incrementally. If your app has an AutoRecovery feature, take advantage of it. If not, save a new version of your project every hour or so with a new file name each time. If a file becomes corrupt, you'll still have a working version available.
 
3) Install Dropbox. Snapshots of changes in your local Dropbox folder are kept for 30 days. If a file is damaged or deleted, you can restore a previous snapshot: https://www.dropbox.com/help/11/en.
 
4) Don't leave the app open and unattended for long periods of time. Some users have reported file corruption after leaving their apps open overnight. It's possible that a malware scan or disk backup could run because the machine is idle, making your app vulnerable to crashing.
 
You could look at importing this file into a new .story file to see if that'll resolve any of the odd behavior you're experiencing. 

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