Bug #2738: A wrong version number was set when importing a SCORM package - Repository - Chamilo Tracking System

Bug #2738

A wrong version number was set when importing a SCORM package

Added by Goulwen Reboux about 9 years ago. Updated almost 9 years ago.

Status:

Bug resolved

Priority:

Normal

Assignee:

Stefaan Vanbillemont

Target version:

2.1.0

Start date:

03/02/2011

Due date:

% Done:

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

scorm-import.patch (854 Bytes) scorm-import.patch

Goulwen Reboux, 03/02/2011 15:46

Associated revisions

Revision 5178a591 (diff)
Added by Julio Montoya over 1 year ago

Improve composer update speed see #2738

Revision 26eb4994 (diff)
Added by Yannick Warnier over 1 year ago

Add Guzzle as main dependency to avoid depending on dev environment for version-checker AJAX call - refs #2738

History

Updated by Goulwen Reboux about 9 years ago

Goulwen Reboux wrote:

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.