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

SCORM 1.3 cmi.launch_data incorrect

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.8.9, 2.9.3, 3.0.1
    • Fix Version/s: 2.9.6, 3.0.4
    • Component/s: SCORM
    • Testing Instructions:
      Hide

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

      Using the attached package

      1. add the attached SCORM2004 zip file (SCORM2004-sample) as a SCORM package to your site.
      2. Enter the SCORM package as a student
      3. Ensure that the package loads the first screen and a JavaScript pop-up does not appear. (see screenshot for JavaScript error that occurs prior to this patch)
      4. You do not need to "test" the SCORM package further - SCORM 2004 is not fully supported and other issues may occur.

      (Alternative instructions, NOT required) Using the Prodding SCO

      1. Download the Prodding SCO, precisely the SCORM 2004 package:
      2. Extract the archive and change the imsmanifest.xml file to read:

        ...
              <item identifier="DB4B88FC-DD3A-11DA-9B41-B622A1EF5492" identifierref="EA10429C-DD3A-11DA-9B41-B622A1EF5492">
                <title>SCORM Diagnostic SCO</title>
                <adlcp:dataFromLMS>Some SCO Information</adlcp:dataFromLMS>
              </item>
        ...
        

      3. Select all the extracted files, including the XML file just changed, and create a new SCORM archive representing our customized package
      4. Add a new SCORM activity using the customized package above
      5. Enable SCORM API debugging, including debugging at DEVELOPER level. Be sure to allow browser popups before starting the next step
      6. Attend to it as a student using FF cleaning its cache first - Note: CR has sometime issues with giving the right room to visualize the SCO in the Moodle player - , the prodding SCO will appear
      7. Click on the API Prodder tab and issue a sequence of:
        • Initialize
        • GetValue, using cmi.launch_data as data element. You should get the value set in the manifest file i.e. Some SCO Information
        • Terminate
      8. Ensure that everything is fine e.g. no debugging messages on the API logging windows
      Show
      (difficulty: easy, requires teacher access to a course) Using the attached package add the attached SCORM2004 zip file (SCORM2004-sample) as a SCORM package to your site. Enter the SCORM package as a student Ensure that the package loads the first screen and a JavaScript pop-up does not appear. (see screenshot for JavaScript error that occurs prior to this patch) You do not need to "test" the SCORM package further - SCORM 2004 is not fully supported and other issues may occur. (Alternative instructions, NOT required) Using the Prodding SCO Download the Prodding SCO , precisely the SCORM 2004 package : Extract the archive and change the imsmanifest.xml file to read: ... <item identifier="DB4B88FC-DD3A-11DA-9B41-B622A1EF5492" identifierref="EA10429C-DD3A-11DA-9B41-B622A1EF5492"> <title>SCORM Diagnostic SCO</title> <adlcp:dataFromLMS>Some SCO Information</adlcp:dataFromLMS> </item> ... Select all the extracted files, including the XML file just changed, and create a new SCORM archive representing our customized package Add a new SCORM activity using the customized package above Enable SCORM API debugging , including debugging at DEVELOPER level. Be sure to allow browser popups before starting the next step Attend to it as a student using FF cleaning its cache first - Note: CR has sometime issues with giving the right room to visualize the SCO in the Moodle player - , the prodding SCO will appear Click on the API Prodder tab and issue a sequence of: Initialize GetValue , using cmi.launch_data as data element . You should get the value set in the manifest file i.e. Some SCO Information Terminate Ensure that everything is fine e.g. no debugging messages on the API logging windows
    • Affected Branches:
      MOODLE_28_STABLE, MOODLE_29_STABLE, MOODLE_30_STABLE
    • Fixed Branches:
      MOODLE_29_STABLE, MOODLE_30_STABLE
    • Pull from Repository:
    • Pull Master Branch:

      Description

      The cmi.launch_data is not properly set for SCORM 1.3 in both mod/scorm/datamodels/scorm_13.js and mod/scorm/datamodels/scorm_13lib.php

      SCORM modules that use cmi.launch_data will NOT work.

        Attachments

        1. Capture.PNG
          Capture.PNG
          798 kB
        2. scorm13patch.txt
          1 kB
        3. SCORM2004-sample.zip
          62 kB

          Activity

            People

            • Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Fix Release Date:
                9/May/16