TOPIC:

Hello everyone,

I am a relatively new user of xerte and need some help, please.
My colleagues and I noticed a little glitch in the testing version of our online tutorial created in xerte (Toolkit). It seems that if participants choose to go back in slides using a back arrow < it prevents them from being able to select an answer to a question on the following slide. Could this be easily fixed?
All the functionality of the interactive elements is fine in the xerte itself, but once put in the LMS - it no longer works.
Does anyone have any ideas of how to fix this?

Many thanks in advance!
Dominika

Hi and welcome.
I take it you have two separate issues.
1. When navigating back it prevents from answering the wution on the follwing slide.
2. All seems to work fine (except issue 1) within Xerte, but in the LMS it no longer works.

We do need more details to be able to help you :-)

1. Which pagetype are navigating back to, and what is the next page (mcq or quiz)?

2. What LMS are you usng, and how did you put the Xerte project into the LMS? Just as a link? Using SCORM? Using LTI?

Let me know, and I'll try to help you.

Cheers,

Tom

Hi Tom,

Thank you very much for getting back to me.

1. It seems that whichever page we go back to (usually a plain text slide with a photo or a navigator page with tabs) the situation is the same. The questions are on interactivity pages, some single answers, some multiple and some gap fills and sorting into columns too.

2. Cornerstone LMS, uploaded SCORM 1.2

Does it all make sense? Do you need any screenshots?

Many thanks for looking into this for me.

Dominika

Thanks for helping with this, Tom. I've recorded the issue with Dominka.

york-ac-uk.zoom.us/rec/share/TcefDEtQZqt...rtTime=1666275896000
Passcode: D0r18k@*

This behaviour happens whether the scorm object is on Cornerstone, Scormcloud or Blackboard, so it's persistent and likely to be something with the way the MCQ page is coded?
I'm wondering if the MCQ page needs to 'refresh' each time since it doesn't hold on to the answer the person gave anyway.
Regards
Lilian

With many thanks to Fay in helping us with a temporary fix.
Add the script optional property to your MCQ pages and paste in this code:

$('#optionHolder input').prop( 'disabled', false );

Also, make sure the Script execute drop down is set to ‘every time the page is viewed’. Check that this doesn’t cause any other problems.

This has been reported as a bug so hopefully will be fixed in future releases.