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

SCORM activities no longer seem to commit the results.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Blocker
    • 2.4
    • 2.4
    • SCORM
    • MOODLE_24_STABLE
    • MOODLE_24_STABLE
    • master_MDL-36772
    • Hide

      Turn jscache on
      enter SCORM package.
      view source of page to find direct link to cached request.js file - looks like this:
      /lib/javascript.php/1353655141/mod/scorm/request.js

      open file directly in browser and make sure JS exists in the cached file.

      • before this patch in master the following text is shown in the cached file:
        Parse error: Missing operand in file '[inline]' on line 1
      Show
      Turn jscache on enter SCORM package. view source of page to find direct link to cached request.js file - looks like this: /lib/javascript.php/1353655141/mod/scorm/request.js open file directly in browser and make sure JS exists in the cached file. before this patch in master the following text is shown in the cached file: Parse error: Missing operand in file ' [inline] ' on line 1

    Description

      All of the SCORM packages that I have tried no longer seem to finish and check off as done.
      I had a talk to Ankit and he directed me to the API debug section.
      It seems that none of the information is being commited to moodle anymore.
      I tested this on 2.3 and that seems to be working.

      Attachments

        Issue Links

          Activity

            People

              danmarsden Dan Marsden
              abgreeve Adrian Greeve
              Ankit Agarwal Ankit Agarwal
              Sam Hemelryk Sam Hemelryk
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Clockify

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