I have just published a quiz for a client, however when we have reviewed it, the review course button is not allowing us to review the quiz. Furthermore, the exit course trigger is also not working
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?
Thanks Andrew! I am able to see the issue now as well. I will get this reported to our team, but unfortunately I do not have a workaround to offer this time.
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:
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.
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.
34 Replies
Hi Andrew!
Do you have a .story file that you'd like us to take a look at?
Hi Leslie
I have just tested in tempshare, and its nots working.
http://s3.amazonaws.com/tempshare-stage.storyline.articulate.com/sto_1b2ol7kv71or71k4glteo6r38p6t/story.html
I have attached the zip file for you to review.
Many Thanks
Looks like that's the published output Andrew. I'd like to take a look at the .story project file that you worked on prior to publishing.
sorry
I thought you would want to look at that
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.
Thank you so much for your help with this matter.
have a great rest of the day
Thanks for your help.
I implemented the changes as stated however the issue remains. Both the review and exit course options do not work
Sent from my iPhone
Did you experience the issue with the published file that I shared?
Hi.
I added the changes to my story file you recommend and re published. I have replicated this in as2 and I have no issues at all.
Bit concerned that I may have to rewrite all my clients modules on as2 and the time that will take.
Sent from my iPhone
Hi Andrew!
I did a recording going through the link that I shared above and you can see that it is working well for me in Chrome:
https://360.articulate.com/review/content/c9510287-6956-4806-b4a9-1101f005d301/review
What browser are you viewing the content in?
I am viewing in windows ie 10
Sent from my iPhone
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?
Hi Leslie,
thanks for staying with me on this....
When I have reviewed your published files, they work fine, as do mine in tempshare,
I have done a quick video screen recording to show the issue I am having. Hope it helps.
just a quick update,
we have just tested your link in firefox and chrome and the review button does not work
Many Thanks
Thanks Andrew! I am able to see the issue now as well. I will get this reported to our team, but unfortunately I do not have a workaround to offer this time.
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.
Hi Leslie,
yes your file works fine.
Many Thanks
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
Hi Leslie.
I replicated what you had done. That being import the file again and it worked once published.
Thank you for your help with this.
Can you provide any thoughts what the issue could have been?
Sent from my iPhone
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.
Hi,
I am having the same problem with this quiz and the review button. When you click on it it takes you to the previous slide. Any help appreciated.
Cheers,
Pip Fowler
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
Hi Wendy, thanks so much. Could you send through the file with the fix. Cheers, Pip
Hi Pip
I've only worked on one layer of the first Q1 - correct layer
Hi Wendy,
Thanks for that. Do I need to create a trigger like the one you have done on all the layers? Or just the ones that show correct?
Cheers,
Pip
This discussion is closed. You can start a new discussion or contact Articulate Support.