Project

General

Profile

Bug #2738

A wrong version number was set when importing a SCORM package

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

Status:
Bug resolved
Priority:
Normal
Assignee:
Stefaan Vanbillemont
Target version:
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

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

#1

Updated by Goulwen Reboux over 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.

#2

Updated by Stefaan Vanbillemont over 9 years ago

  • Target version set to 21
#3

Updated by Stefaan Vanbillemont over 9 years ago

  • Project changed from Chamilo LCMS Connect to Repository
  • Category deleted (4)
#4

Updated by Goulwen Reboux over 9 years ago

Patch added and pushed.

#5

Updated by Goulwen Reboux over 9 years ago

  • Status changed from New to Needs testing
  • Assignee set to Stefaan Vanbillemont
#6

Updated by Stefaan Vanbillemont over 9 years ago

  • Status changed from Needs testing to Bug resolved
#7

Updated by Stefaan Vanbillemont about 9 years ago

  • Target version changed from 21 to 2.1.0

Also available in: Atom PDF