Retry assessment trigger not working in Safari on iPad

May 16, 2013

James Grafe
By James Grafe

Weird thing is that it works in Safari 5, IE 8, Chrome 26 and Firefox 21 on Windows XP.

I have two triggers on a Retry Assessment button; (1) reset results when they click this button, and (2) jump to the question draw when they click the button.

Is there a better way to send learners back to the question draw?

5 Replies
Christine Hendrickson
almost 11 years ago05/16/13 at 12:44 pm (UTC)

Hi James,

Can you please confirm that you're running the most recent version of Storyline? 

To find this information, click on "Help" and "About Articulate Storyline". If you're not running version 2 (1212.1412), please download and install the update using the link below. Once you've finished installing the update, please republish your course and test it on the iPad.

Download Storyline Update 2

If that doesn't resolve the problem, it may be related to this issue. 

Let me know if you see any improvements after updating (if you haven't already).

Thanks!

James Grafe
almost 11 years ago05/16/13 at 1:22 pm (UTC)

Thanks Christine,

I have UPDATE 2: 1302.2803 on my Windows XP SP3 machine.

On further testing, the Retry button does not work when I open the story_html5.html file in Safari 5 on Windows XP.

Is there another workaround in addition to:

  1. View the Flash version of the course in a supported browser
  2. View it in the Articulate Mobile Player on an iPad
Christine Hendrickson
almost 11 years ago05/16/13 at 1:55 pm (UTC)

Hi James,

I'm sorry, but no, not that I'm aware of.

The only things that come to mind may not be appealing to you for your course. For example, you could have the course close and you could disable resume for the course. The learner could attempt the course again, but that could be very tedious to the learner if the course is large. 

You could branch to a "copy" of the quiz, but there may be issues with tracking, reporting and scoring if you do that. 

You could also try using questions outside of a question bank, but since this issue is related to HTML5, I'm not entirely sure that would actually resolve the issue. It seems to be a combination of the two that causes the problem, but I'd hate to see you rebuild the questions and then have the same issue. 

If you'd like, you're welcome to send us your .STORY file. We'd be happy to take a look and see if there's something we can suggest for the course.

Thanks, James!

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