Bug #2738
A wrong version number was set when importing a SCORM package
Start date:
03/02/2011
Due date:
% Done:
0%
Estimated time:
Complexity:
Normal
Description
The SCORM version number sets in the DB when importing uses the version
attribute of the xml
root node, instead of the @LOM->medatada->schemaversion
@. The patch provided correct this bug.
Files
Associated revisions
Add Guzzle as main dependency to avoid depending on dev environment for version-checker AJAX call - refs #2738
History
Updated by Goulwen Reboux almost 12 years ago
Goulwen Reboux wrote:
The SCORM version number sets in the DB when importing uses the
version
attribute of thexml
root node, instead of theLOM->medatada->schemaversion
. The patch provided correct this bug.
Updated by Stefaan Vanbillemont almost 12 years ago
- Project changed from Chamilo LCMS Connect to Repository
- Category deleted (
4)
Updated by Goulwen Reboux almost 12 years ago
- Status changed from New to Needs testing
- Assignee set to Stefaan Vanbillemont
Updated by Stefaan Vanbillemont almost 12 years ago
- Status changed from Needs testing to Bug resolved
Improve composer update speed see #2738