Unintended auto advancing

alewis7977
alewis7977 Community Member Posts: 3
Cheers!

On the slide containing the last question of a test, the user clicks a next button to 1) process the test question and 2) process the entire test.

User is then prompted to click anywhere on screen (button covers entire page) which calls on action that if question was answered correctly to: 1) modify variable to reflect a randomly generated number & 2) go to next page. Or if last test question was incorrect, stay on current page.

In view mode the content functions as expected. However when I publish and view with Chrome or IE browsers, the last test question page is automatically advancing after user clicks next, and not waiting for user to click the whole screen button. The random number is still being generated as expected though, but my question is what can I do/check to prevent automatic advancing please?

I have attempted many fixes but to no avail, any input is much appreciated.

Thank you kindly,
Angi

 

 

Comments

  • jvalley4735
    jvalley4735 Community Member Posts: 1,310 ♪ Opening Act ♪
    In what order do you have the actions firing?  Sometimes within the product, they'll all fire correctly however the browser will want them specifically ordered to do what you're looking to achieve.
  • alewis7977
    alewis7977 Community Member Posts: 3
    Hello,

     

    Thank you kindly for responding. When user clicks Next, the 1st action is to process the question, followed by processing the test and then showing elements based on if the question was answered correctly or incorrectly.

    I played around with the order and have only been able to stop the auto advance when I publish the file without the process test action, ideas?

    Kind Regards,

    Angi

     
  • jvalley4735
    jvalley4735 Community Member Posts: 1,310 ♪ Opening Act ♪
    Is it possibly because the test level behaviors are overriding the page level behaviors?  Try going to the behavior tab, selecting no action from the on completed and the same for on failed.
  • alewis7977
    alewis7977 Community Member Posts: 3
    Thank you for your time and the idea! When I navigate to assign action upon completion I do not see that as an option.

    Additionally, this file worked as expected until the last Lectora update. It is only once I published file for the first time after update that this became an issue.

     
  • elearnchick
    elearnchick Community Member Posts: 10 ♪ Opening Act ♪
    Hello,

    I have the same issue:

    When I publish and step through the program, the page (before last) that processes the test  auto-advances. The last page, which marks the status as complete also auto-advances but the course still gets marked "completed" in the LMS (GeoLearning/Maestro/SumTotal Growth Edition). See page structure in attachment.

    So basically, after completing the single question test, the last two pages of the module auto-advance.

    This module is a copy from last year with the exception of two new text pages inserted within the test prior to the question.

    In checking the behavior properties of the test, I'm unable to change the action - only the target - as the action button is not clickable and statically set to "Go To" (see attachment).

    Hoping someone can assist/advise.

    Thanks,
    -Sandi.
  • jvalley4735
    jvalley4735 Community Member Posts: 1,310 ♪ Opening Act ♪
    The system by default will send you to the next page (in Lectora Publisher or Inspire) or to one of the pages created (in Lectora Online). This is so you can specify where you want the learner to go after the test is completed/passed or canceled/failed.  If you'd like the navigation to happen otherwise you can either send both options to a landing page where they can branch off or see content controlled by variables.  Another option is to create a blank page that loads but have a redirect on it to happen right away.
  • elearnchick
    elearnchick Community Member Posts: 10 ♪ Opening Act ♪
    Hmm. I copy the module year-after-year and don't remember changing any of the logic but this year, the behavior seems to work differently from previous years (using Publisher and then Inspire).

    The good thing is, I was successful at getting it to work to my expectations by changing both the Completed and Canceled destinations on the Behavior tab to "Current Page." Now the page no longer auto-advances.

    All is good in the world. :-)

    Thank you for following up!