Project

General

Profile

Actions
Copy link

Bug #20021

closed

Select doesn't allow comma in value

Added by Steffen Kamper over 15 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2009-02-15
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.3
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

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

Download all files
10442.diff (1.38 KB) 10442.diff Administrator Admin, 2009-02-15 22:04
T3X_sk_test_core-0_0_0-z-200902152204.t3x (13.1 KB) T3X_sk_test_core-0_0_0-z-200902152204.t3x Administrator Admin, 2009-02-15 22:05
10442_v2.diff (2.06 KB) 10442_v2.diff Administrator Admin, 2010-01-06 14:50

Related issues 1 (0 open — 1 closed)

Related to TYPO3 Core - Bug #18016: FCE-Dropdown shows Invalid Value Error when using commaClosed2008-01-18

Actions
Actions
Copy link

Also available in: Atom PDF