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

Assets should be launched w/o waiting for the RTE support

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.4.3
    • Fix Version/s: 2.5
    • Component/s: SCORM
    • Labels:
    • Testing Instructions:
      Hide

      (Difficulty: easy, requires administrator to configure SCORM debuggign and access to a course)

      1. Open Internet Explorer and cleanup its cache
      2. Log as Administrator and activate SCORM API Debugging
      3. Log into a Course, e.g. a Topics one, and Turn Editing on.
      4. Create a new SCORM activity with the attached SCORM package v2, MDL-38678_v2.zip e.g. DnD the file into a Topic.
      5. Click on this new SCORM activity and attend to it: a new popup|tab will be opened too (the SCORM API Activity Log)
      6. The first item will be launched: the Prodding SCO will appear
      7. Click on the API Prodder tab of the SCO
      8. Click Initialize button
      9. Click the SetValue session time: 0000:hh:mm:ss.ss link
      10. Click the Terminate button
      11. Click on the Next button in the navigation bar: the PDF will appear inline.
      12. Click on the Next button in the navigation bar: the Prodding SCO will appear after few seconds, there's no icon status in the TOC (SCO being declared as Asset).
      13. Click on the API Prodder tab of the SCO
      14. Click Initialize button
      15. Click the SetValue session time: 0000:hh:mm:ss.ss link
      16. Click the Terminate button
      17. check the SCORM API Activity Log tab/popup to make sure the error "Item ITEM3 has been defined as an Asset: it should never call the SCORM API" appears in the activity log
      18. Exit the Activity
      19. Open the SCORM Basic report and look at the attempt of the user above to see tracking data for the 3 items, the 2nd just completed
      Show
      (Difficulty: easy, requires administrator to configure SCORM debuggign and access to a course) Open Internet Explorer and cleanup its cache Log as Administrator and activate SCORM API Debugging Log into a Course, e.g. a Topics one, and Turn Editing on. Create a new SCORM activity with the attached SCORM package v2 , MDL-38678 _v2.zip e.g. DnD the file into a Topic. Click on this new SCORM activity and attend to it: a new popup|tab will be opened too (the SCORM API Activity Log ) The first item will be launched: the Prodding SCO will appear Click on the API Prodder tab of the SCO Click Initialize button Click the SetValue session time: 0000:hh:mm:ss.ss link Click the Terminate button Click on the Next button in the navigation bar: the PDF will appear inline. Click on the Next button in the navigation bar: the Prodding SCO will appear after few seconds, there's no icon status in the TOC (SCO being declared as Asset). Click on the API Prodder tab of the SCO Click Initialize button Click the SetValue session time: 0000:hh:mm:ss.ss link Click the Terminate button check the SCORM API Activity Log tab/popup to make sure the error "Item ITEM3 has been defined as an Asset: it should never call the SCORM API" appears in the activity log Exit the Activity Open the SCORM Basic report and look at the attempt of the user above to see tracking data for the 3 items, the 2nd just completed
    • Affected Branches:
      MOODLE_24_STABLE
    • Fixed Branches:
      MOODLE_25_STABLE
    • Pull from Repository:
    • Pull Master Branch:
      m25_MDL-38678_SCORM_RTE_not_required_for_SCO_Assets

      Description

      The current implementation in mod/scorm/loadSCO.php wait for RTE to be ready to accept tracking data for Assets too: it is nicer (read better, see below) to directly jump to the untracked resource.

      This improvement will also resolve a bug when using PDF assets under IE: see https://moodle.org/mod/forum/discuss.php?d=224887 for details.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

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

                  Dates

                  • Created:
                    Updated:
                    Resolved:
                    Fix Release Date:
                    14/May/13