yes, please. cuz, if i do “Los Angeles, CA, USA” – “San Francisco, CA, USA”, it will show like “LosAngelesCAUSA” – “SanFranciscoCAUSA”… that’s weird, and not cool, lol. instead of replacing the commas or other character, just two normal text box input? that will make this field more flexible, more useful…
The field is unable to handle values with comma.
Since our initial assumption was date, we stored the values as comma separated value( e.g 3-4) is stored as (3,4).
The field id provided in the display callback is not reliable and we cloud not use the meta due to that. For now, I do not see a simple solution for fields containing comma( we can not change the storage structure a it will break old installs).
You must be logged in to reply to this topic.