Issue Bug Closed

#20021Select doesn't allow comma in value

Steffen Kamper 02/15/09, 22:03 updated 08/26/14, 20:16

Description

This has a reason: multiselects (select with maxitems>1) are saved as comma-seperated list.
Proceeding the value while save and read use an explode on the comma to seperate the values again.

This doesn’t make sense for single selects. As they could be used also in a FCE, where the value isn’t processed in an extension but passed directly to FE, usage of comma in value makes sense.

Attached patch differenciate between single and multiselect and explode the value only for selects having maxitems>1

Use attached extension for test
(issue imported from #M10442)

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.