Hi all I have disabled the Prev and Next button for all the slides. I have created a custom button to allow reset the quiz. I published the project to both html5 and flash. The flash version works perfectly fine but the issue with HTML5 version is that the "Prev" and the "Next" button would appear after revisiting the quiz (as seen in the picture). They only appear after revisit the quiz. I am using Storyline Update 1. Is it a bug of this version or I have done something wrong. Thanks. Yang

Hi Marge, Since I can't see your project file I am going in blind with my answer, but maybe it can help. Possible fix When you are enabling the option to 'ALLOW USERS TO REVIEW QUIZ' (found under the options on the result slide) you are actually creating an extra layer for each of your question slides. And in contrary to popular belief, you can manipulate this layer and do anything you want with it on this layer (like adding an extra button with a trigger that brings the user to any place you want). How to see this extra layer in your project For each question, make sure the view is set to 'FORM VIEW'. Then look for the FEEDBACK AND BRANCHING options found at the bottom of the form. Underneat the CORRECT and INCORRECT feedback you will see a box POST-QUIZ REVIEW. This box is empty by default. This means that you will never see this when you go back to SLIDE VIEW. What you however do see on the slide view (automatically) is the CORRECT and the INCORRECT layer. This makes sense because there is something to display on these layers since the feedback text is pre-filled. Now comes the clue of the story. If you type something in the POST-QUIZ REVIEW box there is a new layer added to the SLIDE VIEW. Storyline will now add a new layer called REVIEW. Now you can play around with this layer and have full control on what you want to achieve in your project when users are reviewing a particular question. Extra tip The REVIEW layer added by using the POST-QUIZ REVIEW field listens to the REVIEW FEEDBACK layout in your FEEDBACK MASTER. If you work with master slides, you now know where to change the default look and contents of this layer. Let me know if this was helpfull in any way!

I don't understand the reasoning behind forcing the default navigation buttons to appear because "Storyline may not know that you set up your own custom buttons." Then why does the feature to turn off the default navigation exist? Wouldn't any page potentially be without navigation if that's the reasoning you're using?

I know this is an old thread.. but if anyone is still listening, I'm wondering how to set a trigger for that Next button that appears by default when revisiting a quiz slide. I've got a scene that has a series of quiz questions. You access that scene from a main menu slide in another scene. And at the end of the quiz questions, I want users to be able to return to that main menu slide again. This works fine first time through... the Continue button has a trigger that returns them to the main menu slide. If they revisit the Quiz scene, they can review each of their questions/answers, clicking Next to go from question to question. This is fine. But when they get to the last question, the Next button doesn't do anything. And there is no way to add a trigger to the Next button on that slide to send it back to the main menu slide... because the Next button was turned off for all of the quiz questions. It's only showing up because it is the default behavior in Storyline, as noted above. As a possible solution, is there a way to add a button on that last slide that will only display when the quiz question is being revisited? And then I could add a trigger to that button? Thanks for any help here.

I found a solution to this. I chose to enable the prev and next buttons on my slide and then used triggers to hide them when slide starts. this over-rides the review mode showing the buttons on the slide.

Hi Yang, I'd recommend installing the latest update to Articulate Storyline (Current version is update 5) which has numerous performance improvements and has fixed several bugs related to quizzes in HTML5. Hopefully the updated version will resolve your issue with the buttons.

Prev and Next button appear after revisit the quiz.

DamonCrumley
Community Member
10 years ago
Another person on my team (Dane Boyington) has commented elsewhere on issues we have using custom navigation. It's just very frustrating how much relies on automated features that can't be accessed or replicated through custom navigation. To have the default navigation appear when the developer has expressly disabled that feature could compromise an entire course. The default navigation won't have any custom triggers applied to them that the developer may require. In our work, we use an "IsQuestionActive" variable to determine whether the user has interacted with a quiz in a particular way. We disable default navigation to ensure that this variable has integrity. If Storyline's default navigation can appear in certain situations, then the user could bypass the custom navigation we've setup with its attached triggers. This would make our "IsQuestionActive" untrustworthy, and could cause the user to get trapped on a page (which is ironically the situation you claim this behavior seeks to avoid).
LeslieMcKerchie
Staff
10 years ago
Hi Damon! I do not see any recent threads by a user with that name, so I was unable to dig a bit deeper into what may be going on with your team, but if you were to disable the Quiz Review, that would eliminate the issue discussed on this thread. You may also want to take a glance at this tutorial and see if states may better fit your needs.
jobvlaming
Community Member
9 years ago
Hi,

This issue still persists with update 7. My setup is similar to Damons and Yangs: I want learners to be able to revisit quiz and survey slides without resubmitting them. The default buttons still reappear in html5. Any progress on this?

Thanks, Ayoub
- PaulDouglas-ed1
  Community Member
  9 years ago
  I've been having this issue for some time (SL7 too like yourself) and decided to take a brute force approach which seems to be working well so far.
  
  Rather than having to modify the generated HTML output each time (yuck! Who wants to do that?) I add code in the Master slide:
  
  In the Master slide, I add a trigger to Execute Javascript and add the following code:
  
  // since the Quiz in review mode shows the default SL Prev/Next buttons (SL2 Update 7) we force them to hide
  var currentStyle = document.getElementsByTagName('style')[0].innerHTML;
  //only modify the style tag the FIRST time
  if(currentStyle.indexOf("controls") === -1){
  document.getElementsByTagName('style')[0].innerHTML = currentStyle + "#controls{ display:none !important;}";
  }
  
  All it does is modify the <style> tag in the HTML5 output, and adds styling for the #controls <div> that houses the pesky Storyline default navigation and sets it to hide. I also add a check to only add this style once rather than potentially many times on a new page visit which could lead to trouble.
  
  Hope it helps.
  
  Cheers
  - SudhakarReddy
    Community Member
    9 years ago
    Dear Paul Douglas,
    
    Thank you for providing great solution to hide controls in review mode. If possible can you please let us know how show the controls once we exit from review mode.
    
    Look forward for your great solution.
    
    Regards, S
ChristiePollick
Community Member
9 years ago
Hi, Ayoub -- Sorry for your troubles! As this thread is older and some may no longer be subscribed, if there were any participants you wanted to reach out to directly, you are welcome to use the 'Contact Me' link on their individual profile pages.

Otherwise, if you'd like us to take a look at your file, you are free to upload here and we'll be glad to run some testing!
ChristiePollick
Community Member
9 years ago
Thanks for stopping in to share what's been working for you, Paul! I'm sure it will be helpful for others who come across this post in the future. :)
ChristiePollick
Community Member
9 years ago
Hi, Sudhakar -- Thanks for reaching out, and in the event that you would not hear back from Paul, I just wanted to note that you are welcome to reach out to him directly by way of the 'Contact Me' link on his profile page. :)
PaulDouglas-ed1
Community Member
9 years ago
Hi Sudhakar,

I've not been using the built-in navigation buttons at all. They are turned off across the entire course (but annoyingly appear in Review mode anyway - hence my hacky code).

If you're using the built-in navigation for your course, do you even need to hide these buttons in review mode? I thought by default they are still usually needed even in Review mode so the user can navigate forward/backward through the quiz to review each of their answers?

If not, feel free to send me some more details and I'll see if I can assist.

Cheers
- SudhakarReddy
  Community Member
  9 years ago
  Dear Paul,
  
  We are using navigation for entire course except Quiz pool which is having 10 random questions out of 50 with custom submit button. The quiz pool is having question number and it is working properly when we are in review mode. So I decided to add custom next and prev button by using your code. By using your code, question number issue is fixed but bottom navigation button are not appearing after result page.
  
  Hope this information will help you to understand our concern.
  
  Regards, S
  - PaulDouglas-ed1
    Community Member
    9 years ago
    Hey again Sudhukar,
    
    Any chance you could include a cut-down version of your file and I can take a look?
AndrewHelms-f1f
Community Member
9 years ago
Paul,

Can you check out my storyline file and let me know what I'm doing wrong? I have your code set to execute when the timeline starts on the quiz slides, but I'm still getting the prev and next buttons when reviewing those slides.

Thanks!
settingPerformanceObjectives_V3.story36 MB
- SudhakarReddy
  Community Member
  9 years ago
  Hi Andrew,
  
  Sorry for downloading. And the good news is, your file is working like a charm. You just need to open HTML-5 file while testing in offline environment.
  
  Regards, S
AndrewHelms-f1f
Community Member
9 years ago
Sudhakar,

No problem at all! Thanks for looking. I'm having trouble seeing the change. In Chrome, everything seems to disappear and not function. If I test in IE, I get everything on screen but the prev next buttons still show up. When I test in our LMS SuccessFactors, I still get the prev/next buttons too. I am at work and am wondering if IT has somehow disabled any javascript from executing.

-Andrew
- PaulDouglas-ed1
  Community Member
  9 years ago
  Hi Andrew,
  
  The hack I described above is designed only to affect the HTML5 output (story_html5.html) as that ALWAYS shows the built-in PREV/NEXT buttons when reviewing a quiz.
  
  I see that even in your flash version (story.html) if I answer the "Pick One" question, get to the Results slide and then return to the "Pick One" the default buttons return. I do not have this issue in any of my courses and I think it's because I don't EVER use ANY of the built-in Storyline controls on ANY slide as they seem to cause more issues than be of any help.
  
  In your course you use the seekbar and as mentioned here:
  
  https://community.articulate.com/discussions/articulate-storyline/do-not-want-default-navigation-button-when-revisiting
  
  Ashley Terwilliger says:
  Correct - the previous and next buttons are included by default in a quiz review.
  If you don't want them to appear at all, you'd need to remove the other player elements such as the volume control and seekbar, as those are in the same line as where the previous/next buttons would appear
  
  In your course "Story View" I selected all slides and ensure all Slide Navigation and Player Features were turned off, republished and the flash version seemed fine. I think then if you add my code in the Top Master Slide it will also prevent the HTML5 only bug where those prev/next buttons would still appear anyway.
  
  So unless you can also remove all built-in nav elements on your course then I'm not sure this situation can be avoided?
  
  Let me know how you go!
  - AndrewHelms-f1f
    Community Member
    9 years ago
    Yeah, I have to keep that seekbar. That's where I'm running into the issue. I'm confused though. If you don't ever use the default player controls, what's the code for? I thought if you don't use the default controls, then the issue won't affect you?
    
    Or are you saying the issue does still affect the HTML5 version, even if you don't use the default player controls?
    
    Also, if you look at Sudhukar's comment on my project above, he says that the code is working for him when he reviews my quiz slides. Very odd. Haha. I'm going to submit another feature request. It seems like this has been requested several times already. I don't know why it's so difficult to turn off a default option that nobody wants.
AshleyT-Pollard
Staff
9 years ago
Thanks Paul for including that workaround here - I have noticed that it's only worked for some users - so it's a bit sporadic, but again as we'd expect since the default behavior is to always have the prev/next buttons appear on a revisit to a quiz slide since the user will need a way to submit them.