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

Scorm player does not launch for student

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • 2.6.5, 2.7.2
    • 2.6.4
    • SCORM
    • MOODLE_26_STABLE
    • MOODLE_26_STABLE, MOODLE_27_STABLE
    • master_MDL-46961
    • Hide
      1. Please test using Firefox with cache disabled or cleared in browser and cache disabled in Moodle.
      2. Create a SCORM using the options:
        • "Student skip content structure" set to "Always"; and
        • "Display package" option set to "new window"
      3. Make sure pop-up blockers are disabled in browser.
      4. Enter the SCORM as a student (not teacher/admin account)
        • Make sure SCORM package launches in browser correctly.
      Show
      Please test using Firefox with cache disabled or cleared in browser and cache disabled in Moodle. Create a SCORM using the options: "Student skip content structure" set to "Always"; and "Display package" option set to "new window" Make sure pop-up blockers are disabled in browser. Enter the SCORM as a student (not teacher/admin account) Make sure SCORM package launches in browser correctly.

      When the selected value for "Student skip content structure page" is "Always" student could not launch the scorm player and the error displayed in Firebug is "setlaunchoptions is not a function."

      I have solved by placing the setlaunchoptions function above the following if condition
      if (launch == true)

      { setlaunchoptions(); - - - - - }

            danmarsden Dan Marsden
            faisalkaleem Faisal Kaleem
            Dan Marsden Dan Marsden
            Damyon Wiese Damyon Wiese
            Andrew Lyons Andrew Lyons
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved:

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