Parsing Bug found and worked around
Posted: Thu Sep 29, 2011 10:59 pmSynopsis:
If a field name ends with a 'hyphen'+numeral i.e. 'bar-1' or 'bar-2', an error occurs parsing the field name. The field names will be correct in the 'view source' HTML notation - but the rendered value will be incorrect. In the standard context, this is shown by the next field not rendering its name properly - in the Multilingual Context it throws an error with an 'unknown field name'. This may only occur when there are two sequential fields so named. I have not tested that.
Changing the fieldnames to 'bar-uno' and 'bar-dos' resolved the issue. (I did not alter the problem database or app, I just replicated the schema with the fix to a new instance)
I will file a Bug report manana - when I am brain-good again.
If a field name ends with a 'hyphen'+numeral i.e. 'bar-1' or 'bar-2', an error occurs parsing the field name. The field names will be correct in the 'view source' HTML notation - but the rendered value will be incorrect. In the standard context, this is shown by the next field not rendering its name properly - in the Multilingual Context it throws an error with an 'unknown field name'. This may only occur when there are two sequential fields so named. I have not tested that.
Changing the fieldnames to 'bar-uno' and 'bar-dos' resolved the issue. (I did not alter the problem database or app, I just replicated the schema with the fix to a new instance)
I will file a Bug report manana - when I am brain-good again.