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

SCORM cmi.<group>._children string return includes spaces

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 1.9.10
    • Fix Version/s: 2.0.2
    • Component/s: SCORM
    • Labels:
      None
    • Environment:
      Windows 7/IE8
    • Database:
      Any
    • URL:
      http://www.prince2cbt.net log in as fred, password Shirley28*
    • Difficulty:
      Easy
    • Affected Branches:
      MOODLE_19_STABLE
    • Fixed Branches:
      MOODLE_20_STABLE

      Description

      The elements of the return string from LMSGetValue("cmi.<group>._children") are separated by space-comma instead of being comma-separated (i.e. grammatically readable, but bad computer-speak). The following lines are taken from the debug of a course developed in another LMS system; note the unwanted spaces preceding each child after the first, resulting in a 201 invalid argument error:

      LMSGetValue("cmi.core._children") - student_id, student_name, lesson_location, credit, lesson_status, entry, score, total_time, lesson_mode, exit, session_time => 0
      LMSGetValue("cmi.core.student_id") - fred => 0
      LMSGetValue("cmi.core. student_name") - => 201
      LMSGetValue("cmi.core. lesson_location") - => 201
      LMSGetValue("cmi.core. credit") - => 201
      LMSGetValue("cmi.core. lesson_status") - => 201
      LMSGetValue("cmi.core. entry") - => 201
      LMSGetValue("cmi.core. score") - => 201
      LMSGetValue("cmi.core. lesson_mode") - => 201

      The SCORM runtime documentation is not explicit about this, except for the example shown for cmi.core._children, and without space-stripping these spaces break code that processes the return from a _children enquiry.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  21/Feb/11