I'm working on a large project and a lot of my hyperlinked text doesn't fully change color when visited. The letters and number seem to all change from blue to purple, but on many of the links, only part of the underline will change to purple and the rest of the underline remains blue. The client already indicated they aren't going to let it slide and I'm not sure how to fix it. Course content is confidential, otherwise I would love to send screenshots and/or the .story file.
After having a few messages back and forth, here's the last email I just got from John:
Upon checking once more, it appears that your file could have been behaving erratically. To fix this, you can create a new project and import the slides from your original project to the new one. This automatically fixes the issue with the hyperlinks. Here's how.
And with that, it's completely resolved!
Note: I re-sized the new project to match the existing one before hitting import, otherwise it wouldn't work properly.
I guess sometimes Storyline just behaves unexpectedly. I'm glad that there's an Articulate equivalent of hitting reset and I'm thrilled that the bug was living in the file and not in the slides that I imported into a new file. Phew!
Another helpful email from John that came in just now:
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 and copy important projects from your local drive to your Dropbox folder as a backup. 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.
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.
3 Replies
Hi Robbie,
I'm glad you were able to contact our support team as well. I can see that you're currently working with John, so you're in great hands.
SOLVED.
After having a few messages back and forth, here's the last email I just got from John:
Upon checking once more, it appears that your file could have been behaving erratically. To fix this, you can create a new project and import the slides from your original project to the new one. This automatically fixes the issue with the hyperlinks. Here's how.
And with that, it's completely resolved!
Note: I re-sized the new project to match the existing one before hitting import, otherwise it wouldn't work properly.
I guess sometimes Storyline just behaves unexpectedly. I'm glad that there's an Articulate equivalent of hitting reset and I'm thrilled that the bug was living in the file and not in the slides that I imported into a new file. Phew!
Another helpful email from John that came in just now:
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 and copy important projects from your local drive to your Dropbox folder as a backup. 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.
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.
I appreciate you chiming in to share the helpful tips with the community, Robbie.
I'm glad that the issue is resolved!