kMultiLanguage formatter raises missing field warning
1 view
Skip to first unread message
Alexander Obuhovich
unread,
Dec 25, 2009, 5:32:53 PM12/25/09
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to In-Portal Bugs
Class kMultiLanguage, used to process multilingual fields uses only "l<language_id>_FieldName" fields for data processing. Problem happens because kDBBase::GetField doesn't know that and asks for FieldName field (without language prefix) first and raises warning, that field doesn't exists.