Permalink
Browse files

don't throw an exception for a metadata field out of place

Some vendors who generate QTI put all the same meta data values
in all the metadata places. This isn't valid, but can just be
ignored instead of killing the whole converstion process

closes #6807

Change-Id: I60e6d2eda99d463198e9c40d3636410f7eedb9a5
Reviewed-on: https://gerrit.instructure.com/7918
Tested-by: Hudson <hudson@instructure.com>
Reviewed-by: Brian Palmer <brianp@instructure.com>
  • Loading branch information...
1 parent 8cc0b0e commit 7c0a55c27bc787a55ffe83520f2c987d4775cbe1 @bracken bracken committed Jan 6, 2012
Showing with 1 addition and 1 deletion.
  1. +1 −1 lib/imsqtiv1.py
View
2 lib/imsqtiv1.py
@@ -3109,7 +3109,7 @@ def __init__(self,name,attrs,parent):
self.lang=None
self.label=None
self.entry=None
- self.CheckLocation((QTIMetadata),"<qtimetadatafield>")
+ self.CheckLocation((QTIMetadata),"<qtimetadatafield>", False)
self.ParseAttributes(attrs)
def SetAttribute_xml_lang (self,value):

0 comments on commit 7c0a55c

Please sign in to comment.