Moodle
  1. Moodle
  2. MDL-25757

Duplicate CMI values not showing in report (SCORM Module)

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 1.9.10, 2.0, 2.0.4, 2.1.1, 2.2
    • Fix Version/s: 1.9.15, 2.0.6, 2.1.3
    • Component/s: SCORM
    • Labels:
    • Environment:
      Tested under windows using XAMPP and web host. All databases were MySQL.
    • Testing Instructions:
      Hide

      Please, test this under all branches!

      Turn the SCORM debugger on so you can manually pass values into SCORM:

      In the text field for "select data model element to get or set" enter:
      cmi.interactions_0.id
      in the value to set field enter:
      SC_0200_a
      Hit the LMSSetValue() button

      In the text field for "select data model element to get or set" enter:
      cmi.interactions_0.result
      in the value to set field enter:
      wrong
      Hit the LMSSetValue() button

      In the text field for "select data model element to get or set" enter:
      cmi.interactions_1.id
      in the value to set field enter:
      SC_0210_a
      Hit the LMSSetValue() button

      In the text field for "select data model element to get or set" enter:
      cmi.interactions_1.result
      in the value to set field enter:
      wrong
      Hit the LMSSetValue() button

      now hit the LMSCommit() button

      • now check the results of the above

      go to the reports page of the SCORM - in the basic report it lists all the users who have submitted data and the number of "attempts" - (note attempt number is NOT the number of times a user has entered a SCORM) - click on the attempt number and on the following page click on "track details" - Check to make sure The "id" and "result" sub-elements will are written for interaction 0 and interaction 1.

      Show
      Please, test this under all branches! Turn the SCORM debugger on so you can manually pass values into SCORM: In the text field for "select data model element to get or set" enter: cmi.interactions_0.id in the value to set field enter: SC_0200_a Hit the LMSSetValue() button In the text field for "select data model element to get or set" enter: cmi.interactions_0.result in the value to set field enter: wrong Hit the LMSSetValue() button In the text field for "select data model element to get or set" enter: cmi.interactions_1.id in the value to set field enter: SC_0210_a Hit the LMSSetValue() button In the text field for "select data model element to get or set" enter: cmi.interactions_1.result in the value to set field enter: wrong Hit the LMSSetValue() button now hit the LMSCommit() button now check the results of the above go to the reports page of the SCORM - in the basic report it lists all the users who have submitted data and the number of "attempts" - (note attempt number is NOT the number of times a user has entered a SCORM) - click on the attempt number and on the following page click on "track details" - Check to make sure The "id" and "result" sub-elements will are written for interaction 0 and interaction 1.
    • Affected Branches:
      MOODLE_19_STABLE, MOODLE_20_STABLE, MOODLE_21_STABLE, MOODLE_22_STABLE
    • Fixed Branches:
      MOODLE_19_STABLE, MOODLE_20_STABLE, MOODLE_21_STABLE
    • Pull Master Branch:
      master_MDL-25757
    • Rank:
      15175

      Description

      Requested reminder for Dan Marsden from forum issue:

      http://moodle.org/mod/forum/discuss.php?d=164735

      1. MDL-25757.patch
        3 kB
        Evan Irving-Pease
      2. MDL-25757-commented.patch
        5 kB
        Evan Irving-Pease

        Issue Links

          Activity

          Russell Coombe created issue -
          Dan Marsden made changes -
          Field Original Value New Value
          Link This issue is duplicated by MDL-26595 [ MDL-26595 ]
          Helen Foster made changes -
          Labels triaged
          Fix Version/s STABLE backlog [ 10463 ]
          Martin Dougiamas made changes -
          Workflow MDL Workflow [ 66405 ] MDL Full Workflow [ 75534 ]
          Dan Marsden made changes -
          Link This issue is duplicated by MDL-27611 [ MDL-27611 ]
          Dan Marsden made changes -
          Priority Major [ 3 ] Critical [ 2 ]
          Dan Marsden made changes -
          Link This issue is duplicated by MDL-28332 [ MDL-28332 ]
          Dan Marsden made changes -
          Link This issue is a regression caused by MDL-21761 [ MDL-21761 ]
          Dan Marsden made changes -
          Status Open [ 1 ] Waiting for integration review [ 10010 ]
          Pull Master Diff URL https://github.com/danmarsden/moodle/compare/master...master_MDL-25757
          Pull Master Branch master_MDL-25757
          Pull 2.0 Diff URL https://github.com/danmarsden/moodle/compare/MOODLE_20_STABLE...m20_MDL-25757
          Pull from Repository git://github.com/danmarsden/moodle.git
          Pull 2.0 Branch m20_MDL-25757
          Pull 1.9 Branch m19_MDL-25757
          Pull 1.9 Diff URL https://github.com/danmarsden/moodle/compare/MOODLE_19_STABLE...m19_MDL-25757
          Testing Instructions This is a bit of a pain to test - I wonder if Howard or other watchers on this bug might be able to help by testing this?

          Use example.zip scorm from MDL-27611
          attempt the scorm as a student
          Look at db table "scorm_scoes_track" and make sure all interactions are stored correctly for all interactions
          Pull 2.1 Branch m21_MDL-25757
          Pull 2.1 Diff URL https://github.com/danmarsden/moodle/compare/MOODLE_21_STABLE...m21_MDL-25757
          Eloy Lafuente (stronk7) made changes -
          Fix Version/s 1.9.14 [ 10951 ]
          Fix Version/s 2.0.5 [ 10950 ]
          Fix Version/s 2.1.2 [ 10851 ]
          Fix Version/s STABLE backlog [ 10463 ]
          Affects Version/s 2.1.1 [ 10750 ]
          Affects Version/s 2.0.4 [ 10652 ]
          Affects Version/s 2.2 [ 10656 ]
          Eloy Lafuente (stronk7) made changes -
          Status Waiting for integration review [ 10010 ] Integration review in progress [ 10004 ]
          Integrator stronk7
          Currently in integration Yes
          Eloy Lafuente (stronk7) made changes -
          Status Integration review in progress [ 10004 ] Waiting for testing [ 10005 ]
          Evan Irving-Pease made changes -
          Attachment MDL-25757.patch [ 24915 ]
          Eloy Lafuente (stronk7) made changes -
          Status Waiting for testing [ 10005 ] Testing in progress [ 10011 ]
          Eloy Lafuente (stronk7) made changes -
          Status Testing in progress [ 10011 ] Problem during testing [ 10007 ]
          Eloy Lafuente (stronk7) made changes -
          Status Problem during testing [ 10007 ] Integration review in progress [ 10004 ]
          Eloy Lafuente (stronk7) made changes -
          Status Integration review in progress [ 10004 ] Reopened [ 4 ]
          Eloy Lafuente (stronk7) made changes -
          Currently in integration Yes
          Eloy Lafuente (stronk7) made changes -
          Fix Version/s 1.9.15 [ 11252 ]
          Fix Version/s 1.9.14 [ 10951 ]
          Eloy Lafuente (stronk7) made changes -
          Fix Version/s 2.0.6 [ 11250 ]
          Fix Version/s 2.0.5 [ 10950 ]
          Eloy Lafuente (stronk7) made changes -
          Fix Version/s 2.1.3 [ 11251 ]
          Fix Version/s 2.1.2 [ 10851 ]
          Evan Irving-Pease made changes -
          Attachment MDL-25757-commented.patch [ 25848 ]
          Dan Marsden made changes -
          Testing Instructions This is a bit of a pain to test - I wonder if Howard or other watchers on this bug might be able to help by testing this?

          Use example.zip scorm from MDL-27611
          attempt the scorm as a student
          Look at db table "scorm_scoes_track" and make sure all interactions are stored correctly for all interactions
          Turn the SCORM debugger on so you can manually pass values into SCORM:

          Then run the following commands:

          LMSInitialize("", "")
          LMSSetValue("cmi.interactions_0.id", "SC_0200_a")
          LMSSetValue("cmi.interactions_0.result", "wrong")
          LMSSetValue("cmi.interactions_1.id", "SC_0210_a")
          LMSSetValue("cmi.interactions_1.result", "wrong")
          Commit("", "")

          if using 2.2 you can check the interactions report to make sure all these values are reported - if not you will need to view the tracks for the specific user in the standard report.

          Check to make sure The "id" and "result" sub-elements will are written for interaction 0 and interaction 1.


          Use example.zip scorm from MDL-27611
          attempt the scorm as a student
          Look at db table "scorm_scoes_track" and make sure all interactions are stored correctly for all interactions
          Dan Marsden made changes -
          Testing Instructions Turn the SCORM debugger on so you can manually pass values into SCORM:

          Then run the following commands:

          LMSInitialize("", "")
          LMSSetValue("cmi.interactions_0.id", "SC_0200_a")
          LMSSetValue("cmi.interactions_0.result", "wrong")
          LMSSetValue("cmi.interactions_1.id", "SC_0210_a")
          LMSSetValue("cmi.interactions_1.result", "wrong")
          Commit("", "")

          if using 2.2 you can check the interactions report to make sure all these values are reported - if not you will need to view the tracks for the specific user in the standard report.

          Check to make sure The "id" and "result" sub-elements will are written for interaction 0 and interaction 1.


          Use example.zip scorm from MDL-27611
          attempt the scorm as a student
          Look at db table "scorm_scoes_track" and make sure all interactions are stored correctly for all interactions
          Turn the SCORM debugger on so you can manually pass values into SCORM:

          In the text field for "select data model element to get or set" enter:
          cmi.interactions_0.id
          in the value to set field enter:
          SC_0200_a
          Hit the LMSSetValue() button

          In the text field for "select data model element to get or set" enter:
          cmi.interactions_0.result
          in the value to set field enter:
          wrong
          Hit the LMSSetValue() button

          In the text field for "select data model element to get or set" enter:
          cmi.interactions_1.id
          in the value to set field enter:
          SC_0210_a
          Hit the LMSSetValue() button


          In the text field for "select data model element to get or set" enter:
          cmi.interactions_1.result
          in the value to set field enter:
          wrong
          Hit the LMSSetValue() button

          now hit the LMSCommit() button

          - now check the results of the above

          go to the reports page of the SCORM - in the basic report it lists all the users who have submitted data and the number of "attempts" - (note attempt number is NOT the number of times a user has entered a SCORM) - click on the attempt number and on the following page click on "track details" - Check to make sure The "id" and "result" sub-elements will are written for interaction 0 and interaction 1.
          Dan Marsden made changes -
          Status Reopened [ 4 ] Waiting for integration review [ 10010 ]
          Pull Master Diff URL https://github.com/danmarsden/moodle/compare/master...master_MDL-25757
          Pull Master Branch master_MDL-25757
          Pull 2.0 Diff URL https://github.com/danmarsden/moodle/compare/MOODLE_20_STABLE...m20_MDL-25757
          Pull from Repository git://github.com/danmarsden/moodle.git
          Pull 2.0 Branch m20_MDL-25757
          Fix Version/s 2.0.6 [ 11250 ]
          Fix Version/s 2.1.3 [ 11251 ]
          Fix Version/s 1.9.15 [ 11252 ]
          Pull 1.9 Branch m19_MDL-25757
          Pull 1.9 Diff URL https://github.com/danmarsden/moodle/compare/MOODLE_19_STABLE...m19_MDL-25757
          Pull 2.1 Branch m21_MDL-25757
          Pull 2.1 Diff URL https://github.com/danmarsden/moodle/compare/MOODLE_21_STABLE...m21_MDL-25757
          Eloy Lafuente (stronk7) made changes -
          Currently in integration Yes [ 10041 ]
          Eloy Lafuente (stronk7) made changes -
          Status Waiting for integration review [ 10010 ] Integration review in progress [ 10004 ]
          Eloy Lafuente (stronk7) made changes -
          Status Integration review in progress [ 10004 ] Waiting for testing [ 10005 ]
          Fix Version/s 1.9.15 [ 11252 ]
          Fix Version/s 2.0.6 [ 11250 ]
          Fix Version/s 2.1.3 [ 11251 ]
          Eloy Lafuente (stronk7) made changes -
          Testing Instructions Turn the SCORM debugger on so you can manually pass values into SCORM:

          In the text field for "select data model element to get or set" enter:
          cmi.interactions_0.id
          in the value to set field enter:
          SC_0200_a
          Hit the LMSSetValue() button

          In the text field for "select data model element to get or set" enter:
          cmi.interactions_0.result
          in the value to set field enter:
          wrong
          Hit the LMSSetValue() button

          In the text field for "select data model element to get or set" enter:
          cmi.interactions_1.id
          in the value to set field enter:
          SC_0210_a
          Hit the LMSSetValue() button


          In the text field for "select data model element to get or set" enter:
          cmi.interactions_1.result
          in the value to set field enter:
          wrong
          Hit the LMSSetValue() button

          now hit the LMSCommit() button

          - now check the results of the above

          go to the reports page of the SCORM - in the basic report it lists all the users who have submitted data and the number of "attempts" - (note attempt number is NOT the number of times a user has entered a SCORM) - click on the attempt number and on the following page click on "track details" - Check to make sure The "id" and "result" sub-elements will are written for interaction 0 and interaction 1.
          Please, test this under all branches!

          Turn the SCORM debugger on so you can manually pass values into SCORM:

          In the text field for "select data model element to get or set" enter:
          cmi.interactions_0.id
          in the value to set field enter:
          SC_0200_a
          Hit the LMSSetValue() button

          In the text field for "select data model element to get or set" enter:
          cmi.interactions_0.result
          in the value to set field enter:
          wrong
          Hit the LMSSetValue() button

          In the text field for "select data model element to get or set" enter:
          cmi.interactions_1.id
          in the value to set field enter:
          SC_0210_a
          Hit the LMSSetValue() button


          In the text field for "select data model element to get or set" enter:
          cmi.interactions_1.result
          in the value to set field enter:
          wrong
          Hit the LMSSetValue() button

          now hit the LMSCommit() button

          - now check the results of the above

          go to the reports page of the SCORM - in the basic report it lists all the users who have submitted data and the number of "attempts" - (note attempt number is NOT the number of times a user has entered a SCORM) - click on the attempt number and on the following page click on "track details" - Check to make sure The "id" and "result" sub-elements will are written for interaction 0 and interaction 1.
          Ankit Agarwal made changes -
          Status Waiting for testing [ 10005 ] Testing in progress [ 10011 ]
          Tester ankit_frenz
          Ankit Agarwal made changes -
          Status Testing in progress [ 10011 ] Tested [ 10006 ]
          Eloy Lafuente (stronk7) made changes -
          Status Tested [ 10006 ] Closed [ 6 ]
          Resolution Fixed [ 1 ]
          Currently in integration Yes [ 10041 ]
          Integration date 25/Nov/11

            People

            • Votes:
              5 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: