34 Replies
Leslie McKerchie

Thanks Andrew!

I was able to publish and it seems to be working here:

http://s3.amazonaws.com/tempshare-stage.storyline.articulate.com/sto_1b2ot3jn21c021v2vu321v9313as9/story.html

I did have the same issue you experienced as well. I republished utilizing Flash with HTML5 fallback vs HTML5 with Flash fallback. 

I'll get this reported to our team for follow up. In the meantime, perhaps the other publishing option will work well for you.

Leslie McKerchie

Thanks for the details Andrew. I utilized the same link that I shared above and it is working in the IE 10 emulator as well.

https://360.articulate.com/review/content/691ec3b2-4577-4742-a5eb-c4e5a96445f2/review

I'm still not clear if you are having the same issue with the published link that I shared above or if the issue only lies within the file that you are editing/publishing?

Leslie McKerchie

Andrew - I was doing some testing to prepare for the report and created a dummy file to re-create the issue, but not sure that I was able.

Can you take a look at this file and tell me if you experience an issue with the Review button:

http://s3.amazonaws.com/tempshare-stage.storyline.articulate.com/sto_1b309grh67l45fkd1b14q11rmr9/story.html

It's actually published with your initial requirement of HTML5 with Flash Fallback also.

Leslie McKerchie

That leads me to believe it is an issue within your file since I cannot re-create the issue and you do not experience it either - so it's not just environment and browser - it now seems to be the actual file.

I imported into a new file and re-published and it seems to be working as expected:

http://s3.amazonaws.com/tempshare-stage.storyline.articulate.com/sto_1b37mi7k79f11fbu1bba4gj3ab9/story.html

 

Leslie McKerchie

Hi Andrew! Unfortunately file corruption is one of those mysteries that I cannot explain in most cases. We do have some documentation for best practices and I'll include below:

File corruption is unpredictable, and there's no straightforward way to determine what causes it. 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.

Wendy Farmer

Hi Pip

looks like there is no trigger to hide the feedback layers before continuing. I changed the correct feedback layer on Q1 to hide the layer when user clicks button - this trigger sits above the jump to next slide trigger. 

This is what I get when you click review