Bookmarking and lengthy quiz

Nov 15, 2017

Hello heroes!

The context: I have an activity that is essentially one large test. Each question is a table that learners are supposed to correctly fill out. I have it set up as a pick-one question so that the correct answer (a button off stage) is triggered when each cell is filled out correctly. 

The details: Storyline 360, Moodle v 2.5

The issue: The functionality works as intended. However, I'm running into some technical issues when it comes to bookmarking. Because of the length and nature of the test, I want learners to be able to exit and come back to where they left off. It seems, however, that sometimes the bookmarking doesn't really work.

Some learners are being dropped back to a previous question, others are brought to where they left off, but when they get to the results page it's not correctly tracking right/wrong answers (e.g., learner gets 8/10 right, but results page says 2/10). When reviewing, some of the entered questions are not visible.  Other times, you can see a learner's answers and they are all correct, but the system is marking it as wrong. I am positive I have the settings right at the Storyline level.

I've never used the quiz functionality in this way before (i.e., something learners can do in multiple settings) so I'm beginning to worry that that might be the issue here - that the quiz functionality simply isn't meant to allow for multiple visits. Please tell me I'm wrong!

4 Replies
Shneay Kazan
Thank you for your reply, Matthew! I'm actually having seperate issues with my LMS and SCORM 1.2 (see my other post if you're curious ;)) so I am using 2004. However, I just checked my setting again and I'm using the 2nd edition. Do you think switching to 3rd (or 4th) might help resolve the issue?  
Dan Marsden

Hi Shneay,

Matthew is likely correct - this is probably an issue with the suspend_data limits set by the SCORM 1.2 standard.

Moodle doesn't provide official support for SCORM 2004 but all the current stable Moodle releases provide a way to bypass the SCORM 1.2 restrictions on the suspend_data limits... in admin > plugins > activities > SCORM called "SCORM 1.2 standards mode" - if you disable that setting it will increase the limits within Moodle for suspend_data (and other vars) - You will need to upgrade to a recent stable supported release of Moodle because this setting does not exist in Moodle 2.5

But.. the bigger issue is that you are using an unsupported (old) Moodle version contains a number of known security issues that could allow a malicious user to compromise your site, it also contains a number of known SCORM related issues that could affect how your SCORM packages are behaving. You should prioritise an upgrade to a recent supported stable release of Moodle asap.

Shneay Kazan

Hi Dan,

Thank you for your reply! I agree that our version of Moodle is an issue. We've been working with our LMS provider to upgrade to 3.1 and just received word that it's coming soon - so, yay! Thank you so much for the info re: suspend_data limit and 1.2, that will be very helpful when we do make the switch.  

Dan Marsden

I'm surprised to hear you have an "LMS Provider" and aren't hosting this yourself. Most experienced Moodle providers are aware of the issues running unsupported Moodle releases and will make sure their clients are running supported Moodle releases. 2.5 has been out of support for 3 years which is a dangerously long time to be running unsupported web-based software. If running an older Moodle release hasn't been a problem for your LMS Provider and they haven't been the ones pressuring you to upgrade they probably aren't looking after you properly - they should also be updating your site bi-monthly with every minor release that contains security updates.

We occasionally have times when our clients need to run unsupported Moodle versions but these clients are aware of the risk and pay for a premium service that covers the time for our staff to backport serious security issues into their unsupported Moodle site. (I work for a certified Moodle Partner.)

Now is a good time to make sure you don't end up in a similar situation in future - make sure after the upgrade you also have a bi-monthly minor upgrade scheduled in. We automate this on our hosted systems so all our clients sites are updated every time Moodle releases an update.

Then you should also make sure you have a Major Moodle upgrade scheduled at the end of 2018 or during the first few months of 2019 - 3.1 is only supported for security issues until May 2019 - I'd suggest targeting Moodle 3.5 (releases May 2018) which should be another Long term support release and will give you up to 3 years of security fix support before you need to upgrade again.

If this is too difficult for your LMS provider you might want to look at finding another provider - drop me a private message if you want me to give any recommendations..

This discussion is closed. You can start a new discussion or contact Articulate Support.