You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today we noticed the problem that for events requiring a booking, some information entered in the booking form was not transferred to the database. In the edit preview of the bookings in the WP backend, only ‘n/a’ is displayed in the respective fields, and when the bookings are exported, these fields remain empty. I was able to trace the problem to custom fields in the form editor. Fields created by my colleagues that had umlauts (ä, ö, u) or an ß in the label were converted by the programme into special characters (%, &, etc.) in the field ID. I think that the problem is that ISO 8859-1 (Latin-1) is still being used for the display and its identical decimal character value 246 is being inserted directly into the field ID using percent encoding. The umlaut ‘ö’, for example, is then displayed as the value %F6. This has led to important information not being transferred, and we now have to ask our participants to fill out a form again. Please adjust how the programme generates field IDs from labels or fix this encoding error, which causes database fields to remain empty.
The text was updated successfully, but these errors were encountered:
Today we noticed the problem that for events requiring a booking, some information entered in the booking form was not transferred to the database. In the edit preview of the bookings in the WP backend, only ‘n/a’ is displayed in the respective fields, and when the bookings are exported, these fields remain empty. I was able to trace the problem to custom fields in the form editor. Fields created by my colleagues that had umlauts (ä, ö, u) or an ß in the label were converted by the programme into special characters (%, &, etc.) in the field ID. I think that the problem is that ISO 8859-1 (Latin-1) is still being used for the display and its identical decimal character value 246 is being inserted directly into the field ID using percent encoding. The umlaut ‘ö’, for example, is then displayed as the value %F6. This has led to important information not being transferred, and we now have to ask our participants to fill out a form again. Please adjust how the programme generates field IDs from labels or fix this encoding error, which causes database fields to remain empty.
The text was updated successfully, but these errors were encountered: