Forum Discussion

FormationMoortg's avatar
FormationMoortg
Community Member
5 months ago

Continue button in microlearning: redirection issue

In a microlearning module with connected content (one-page module), when you insert and click on a CONTINUE button, you are not directed to the next activity just after this button, but to half of the next section (e.g.: if after a CONTINUE button you place 10 questions, you are directed to question 5).

This applies to all types of content following the CONTINUE button.

Here's an example:
https://rise.articulate.com/share/edklq-eGrfSKlBWU54_rADYWvLysSnuA

  • PhilFoss's avatar
    PhilFoss
    Community Member

    Confirming this behavior. The first continue button doesn't scroll me down at all, then the second continue jumps me down to question 4 of 8. Something tells me this is related to the vertical centering and 100% height styles on each block in the microlearning template.

  • Hello Formation Moortgat,

    Sorry to hear that you ran into this issue. 

    We are monitoring a known bug found in Microlearning courses when using stepped navigation which causes the continue block to skip some blocks if all blocks are linked/connected. I tested your course and it appears to be similar to the behavior described in this thread. 

    The identified workarounds are to either use continuous navigation or disconnect/unlink the blocks. I've added this community post to the bug report so we can notify you as soon as it is fixed. Thanks for raising this with us, and we apologize for any inconvenience this bug may have caused.

     

  • Hi all!

    I tested again, and the problem disappears when you set the navigation to continuous mode (and not step), which makes the most sense when all the blocks are linked. In this case, the next button takes you to the next block :)

    • StevenBenassi's avatar
      StevenBenassi
      Staff

      Hi Formation Moortgat!

      Thanks for following up and sharing the feedback! Glad to hear the suggested workaround has been helping you.

      We'll update this discussion as soon as a fix is in place!