Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-49303

Initialise student_preferences on re-entry

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • 2.7.6, 2.8.4
    • 2.7.5, 2.8.3
    • SCORM
    • MOODLE_27_STABLE, MOODLE_28_STABLE
    • MOODLE_27_STABLE, MOODLE_28_STABLE
    • master_MDL-49303
    • Hide

      (difficulty: easy, requires teacher access to a course)

      1. Add a new SCORM activity using the Prodding SCO, the 1.2 package: http://www.ostyn.com/standards/scorm/samples/ProddingSCOPackageSCORM1.2.zip
      2. Enable API debugging
      3. Attend to it using FF cleaning its cache first - Note: CR has issues with giving the right room to visualize the SCO in the Moodle player - , the prodding SCO will appear. Select the Scripted test tab and run - i.e. press Play after copying - the script below:

        LMSInitialize("")
         
        LMSGetValue("cmi.student_preference.audio")
        LMSSetValue("cmi.student_preference.audio","10")
        LMSGetValue("cmi.student_preference.language")
        LMSSetValue("cmi.student_preference.language","Italian")
        LMSGetValue("cmi.student_preference.speed")
        LMSSetValue("cmi.student_preference.speed","3")
        LMSGetValue("cmi.student_preference.text")
        LMSSetValue("cmi.student_preference.text","1")
         
        LMSFinish("")
        

      4. The SCORM API debugging should present no errors
      5. Exit the activity and repeat the launch using the same attempt but a different script:

        LMSInitialize("")
         
        LMSGetValue("cmi.student_preference.audio")
        LMSGetValue("cmi.student_preference.language")
        LMSGetValue("cmi.student_preference.speed")
        LMSGetValue("cmi.student_preference.text")
         
        LMSFinish("")
        

      6. Look at the SCORM API debugging to read the same values being set above, during the first launch
      Show
      (difficulty: easy, requires teacher access to a course) Add a new SCORM activity using the Prodding SCO , the 1.2 package: http://www.ostyn.com/standards/scorm/samples/ProddingSCOPackageSCORM1.2.zip Enable API debugging Attend to it using FF cleaning its cache first - Note: CR has issues with giving the right room to visualize the SCO in the Moodle player - , the prodding SCO will appear. Select the Scripted test tab and run - i.e. press Play after copying - the script below: LMSInitialize("")   LMSGetValue("cmi.student_preference.audio") LMSSetValue("cmi.student_preference.audio","10") LMSGetValue("cmi.student_preference.language") LMSSetValue("cmi.student_preference.language","Italian") LMSGetValue("cmi.student_preference.speed") LMSSetValue("cmi.student_preference.speed","3") LMSGetValue("cmi.student_preference.text") LMSSetValue("cmi.student_preference.text","1")   LMSFinish("") The SCORM API debugging should present no errors Exit the activity and repeat the launch using the same attempt but a different script: LMSInitialize("")   LMSGetValue("cmi.student_preference.audio") LMSGetValue("cmi.student_preference.language") LMSGetValue("cmi.student_preference.speed") LMSGetValue("cmi.student_preference.text")   LMSFinish("") Look at the SCORM API debugging to read the same values being set above, during the first launch

      We hijacked an old bug that covered this (MDL-35870) and didn't actually fix the original issue - whoops!

      the student preferences - Audio, language, speed, text are not initialised on re-entry to a SCORM package - we need to check to see if these values have previously been set and return the current value.

            danmarsden Dan Marsden
            danmarsden Dan Marsden
            Matteo Scaramuccia Matteo Scaramuccia
            Dan Poltawski Dan Poltawski
            Simey Lameze Simey Lameze
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.