Forum Discussion
Issue with navigation in Rise course
I’ve built a Rise course that includes different learning tracks for multiple languages.
At the start of the course, learners choose their language using a button stack, which directs them to the four chapters belonging to their specific track.
Because of this setup, I’ve turned navigation off so learners only see the chapters relevant to their track rather than all the other language versions. However, I’m now encountering an issue: if a learner goes back to a previous chapter within their track, they’re unable to move forward again. They receive the error message: “Chapters must be completed in order.”
Has anyone seen this before or knows what might be causing it — and more importantly, how to fix it?
One other thing you might try: Turn off the navigation headers. Instead, use a button block at the beginning and end of each lesson where needed to jump to the previous and next lesson.
Otherwise, I said in my earlier reply, it could be a bug, and you should contact support: https://access.articulate.com/support/contact
5 Replies
- JudyNolletSuper Hero
Check that Restrict Navigation setting is Off.
If that doesn't solve the issue, it could be a bug. In that case, I suggest you contact support:
- IngevanBarenCommunity Member
Navigation has been turned off completely:
However, when a learning scrolls upwards at the start of a new chapter, the option to go back to the previous chapter appears:
When they do click to go back to that previous chapter, they are suddenly locked in that previous chapter and can't continue because 'chapters must be completed in order'.
- JudyNolletSuper Hero
One other thing you might try: Turn off the navigation headers. Instead, use a button block at the beginning and end of each lesson where needed to jump to the previous and next lesson.
Otherwise, I said in my earlier reply, it could be a bug, and you should contact support: https://access.articulate.com/support/contact
- IngevanBarenCommunity Member
Thanks! using a button block instead of a continue button solves the issue.
- JudyNolletSuper Hero
You're welcome! Pay it forward when you can. 😊
Related Content
- 5 months ago