| Key: |
MDL-8725
|
| Type: |
Bug
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Priority: |
Blocker
|
| Assignee: |
Piers Harding
|
| Reporter: |
asdf
|
| Votes: |
0
|
| Watchers: |
2
|
|
|
| Database: |
MySQL
|
| Participants: |
asdf, Dan Marsden and Piers Harding
|
| Security Level: |
None
|
| Resolved date: |
14/Mar/07
|
| Affected Branches: |
MOODLE_17_STABLE
|
| Fixed Branches: |
MOODLE_17_STABLE
|
|
the error is located in moodle\mod\scorm\datamodels\scorm_13.js.php, somewhere around theese lines
<?php
$count = 0;
$objectives = '';
foreach($userdata as $element => $value){
if (substr($element,0,14) == 'cmi.objectives') {
preg_match('/.(\d+)./',$element,$matches);
the output javascript that produces the error:
cmi.objectives..N0 = new Object();
cmi.objectives..N0.score = new Object();
cmi.objectives..N0.score._children = score_children;
the api is than broken, and the sco's cannto talk with the lms anymore.
the bug is triggered when the sco sets "cmi.objectives.0.id". the next time you will enter the course, the javascript code will generate an error, and prevent the api from initializing
|
|
Description
|
the error is located in moodle\mod\scorm\datamodels\scorm_13.js.php, somewhere around theese lines
<?php
$count = 0;
$objectives = '';
foreach($userdata as $element => $value){
if (substr($element,0,14) == 'cmi.objectives') {
preg_match('/.(\d+)./',$element,$matches);
the output javascript that produces the error:
cmi.objectives..N0 = new Object();
cmi.objectives..N0.score = new Object();
cmi.objectives..N0.score._children = score_children;
the api is than broken, and the sco's cannto talk with the lms anymore.
the bug is triggered when the sco sets "cmi.objectives.0.id". the next time you will enter the course, the javascript code will generate an error, and prevent the api from initializing |
Show » |
|
when setting cmi.objectives.0.id in a sco, there are javascript errors that prevent the sco from finding the lms
Dan 
can you please check this? - the commit messages suggest this may only be partially fixed in HEAD - more stable files had patches committed than the files in HEAD - haven't had a good look though - you may just be able to close this bug.
thanks!
Dan