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

SCORM completion is not calculated correctly in SCORM with multiple nested SCO levels

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • 2.9.4, 3.0.2
    • 3.0
    • SCORM
    • MOODLE_30_STABLE
    • MOODLE_29_STABLE, MOODLE_30_STABLE
    • MDL-52429-master
    • Hide
      1. Create a new SCORM activity using the attached package
      2. Set the Appearance setting "Display course structure on entry page" to yes
      3. As student, browse and play the different SCOs (elements in the menu)
      4. Check that you don't see the "Start a new attempt" option in the first SCORM view (see attached screenshot, you shouldn't see the Start a new attempt button)
      Show
      Create a new SCORM activity using the attached package Set the Appearance setting "Display course structure on entry page" to yes As student, browse and play the different SCOs (elements in the menu) Check that you don't see the "Start a new attempt" option in the first SCORM view (see attached screenshot, you shouldn't see the Start a new attempt button)

      For more than 2 nested levels the completion status is not correctly calculated, the recursive function does not check the results of recursive calls to check if the status has changed.

      The effect is that the user can start new attempts even if the previous one are not finished

        1. Captura de pantalla 2015-12-07 a las 10.45.18.png
          Captura de pantalla 2015-12-07 a las 10.45.18.png
          54 kB
        2. MMSCORM(1).zip
          158 kB

            jleyva Juan Leyva
            jleyva Juan Leyva
            Dan Marsden Dan Marsden
            David Monllaó David Monllaó
            Mark Nelson Mark Nelson
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved:

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