Bug #20021
closed
Select doesn't allow comma in value
0%
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)
Files
Updated by Xavier Perseguers almost 13 years ago
- Assignee deleted (
Steffen Kamper) - Target version deleted (
0)
Updated by Alexander Opitz over 11 years ago
- Status changed from Accepted to Needs Feedback
The issue is very old, does this issue exists in newer versions of TYPO3 CMS (4.5 or 6.1)?
Updated by Alexander Opitz about 11 years ago
- Status changed from Needs Feedback to Closed
- Is Regression set to No
No feedback for over 90 days.
Updated by George Sofianos about 10 years ago
although i'm working on an old version of 4.5, i checked the code on the latest 4.5 version and this bug seems to still exist. another problem is that the patch attached on this issue is fixing single selects but it's breaking the main template in the website i'm working on.
I changed maxItems to maxitems in class.t3lib_tcemain.php which seem to fix this problem.