Details
-
Bug
-
Resolution: Fixed
-
None
-
Critical
-
Empty termEntry/language/term attribute-nodes are now skipped if found in TBX-files
-
Empty show more show less
Description
If you import a tbx with the following termEntry, TermPortal will not work anymore correnctly:
<termEntry id="4cd72c65-f023-47da-924b-36b6b31a5f9c">
<langSet xml:lang="de-DE">
<ntig>
<termGrp>
<term id="4cd72c65-f023-47da-924b-36b6b31a5f9c">Kaffee Creme</term>
<termNote></termNote>
</termGrp>
</ntig>
</langSet>
<langSet xml:lang="es-ES">
<ntig>
<termGrp>
<term id="4cd72c65-f023-47da-924b-36b6b31a5f9c">Café</term>
<termNote></termNote>
</termGrp>
</ntig>
</langSet>
</termEntry>
The reason is the empty termNote.
It leads to an completely empty datatype in TermPortal, what is not expected by the TermPortal and leads to errors, because important values are NULL.
Since this is only crap data, the import should ensure, that empty termNotes are simply skipped on import.