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

scorm multi sco 1.2 : the next button (in the bottom of the main screen) does not work properly

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • None
    • 3.5.4
    • SCORM
    • None
    • MOODLE_35_STABLE

      Steps to reproduce (confirmed on a demo sandbox in 3.5 Moodle version):

      • Upload this multi sco SCORM 1.2 to a course : https://drive.google.com/file/d/18B2d5S32loQZ2OPOXW6aqtAV96QwS-K5/view?usp=sharing]
      • Click on the first entry link (called Accueil) in the left drawer : view the first SCO in the package
      • Click on the next button in the bottom of the main screen : the next slide (Objectifs) is displayed
      • Click on the next button in the bottom of the main screen : the next slide (Introduction) is displayed
      • Result : the next button in the bottom of the main screen is disabled
      • Click on the second directory link (called L'origine et les types de thé) in the left drawer : nothing happens
      • Click on the third directory link (called La Chine, berceau du thé) in the left drawer : nothing happens
      • Click on the first entry link (called un arbuste nommé camelia sinensis) in the left drawer (inside the third directory link, called La Chine, berceau du thé) : view the second SCO in the package
      • Click on the next button in the bottom of the main screen : nothing happens
      • Result : the next button (in the bottom of the main screen) does not work properly
      • Solution : click twice on the entry in the left drawer in order for the next button (in the bottom of the main screen) to work.

            Unassigned Unassigned
            thomas@edunao.com Thomas
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:

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