Subpage under development, new version coming soon!
Asunto: [BUG] Malformed XML
- 1
Is it new in xml ?
'''
<trainingPosition/>
<isInTrainingSlot>false</isInTrainingSlot>
'''
invalid trainingPosition (missing open page) cause xml valid fail and may broke third parties tools parsing.
'''
<trainingPosition/>
<isInTrainingSlot>false</isInTrainingSlot>
'''
invalid trainingPosition (missing open page) cause xml valid fail and may broke third parties tools parsing.
Yes, also in team-[teamID].xml:
<trainingTypeGk>1</trainingTypeGk>
<trainingTypeDef>5</trainingTypeDef>
<trainingTypeMid>1</trainingTypeMid>
<trainingTypeAtt>5</trainingTypeAtt>
> <trainingPosition/>
That's a normal XML empty tag, Shouldn't be a problem if the parser follows the standards
(editado)
<trainingTypeGk>1</trainingTypeGk>
<trainingTypeDef>5</trainingTypeDef>
<trainingTypeMid>1</trainingTypeMid>
<trainingTypeAtt>5</trainingTypeAtt>
> <trainingPosition/>
That's a normal XML empty tag, Shouldn't be a problem if the parser follows the standards
(editado)
It's not invalid. It's empty tag, parsers should be able to interpret it correctly.
Same in team xml:
<trainingTypeGk/>
<trainingTypeDef/>
<trainingTypeMid/>
<trainingTypeAtt/>
Same in team xml:
<trainingTypeGk/>
<trainingTypeDef/>
<trainingTypeMid/>
<trainingTypeAtt/>
Valid, but not really good practice, it result to an empty value and undefined type.
In my case (php simpleXml) the value is an empty object. And the result was a crash since i expect all values are string... But well..
So we can close; but i see this as a bad practice even if it's 'correct'.
(editado)
In my case (php simpleXml) the value is an empty object. And the result was a crash since i expect all values are string... But well..
So we can close; but i see this as a bad practice even if it's 'correct'.
(editado)
- 1