Bug #18016

FCE-Dropdown shows Invalid Value Error when using comma

Added by Christopher Schnell almost 13 years ago. Updated about 7 years ago.

Should have
Target version:
Start date:
Due date:
% Done:


Estimated time:
TYPO3 Version:
PHP Version:
Is Regression:
Sprint Focus:


When using an FCE-Dropdown list and there is a comma in the Dropdown value, it is not parsed correctly but an "Invalid Value" is shown instead. This happens when using CDATA, I have not tried it without (because I use also html (linebreak) there). This misbehaviour occurs both, when using the character "," as well as the encoding ","

The output is stopped at the character before the comma.

BTW. The TV Version is 1.3.3 but I cannot select it in the Product Version above.

This Bug was already reported in 2006 by Klaus Hinum on the TV Mailinglist, see http://lists.typo3.org/pipermail/typo3-project-templavoila/2006-May/000928.html

please find below the corresponding part of the XML

<field_aField type="array">
<tx_templavoila type="array">
<TCEforms type="array">
<config type="array">
<items type="array">
<numIndex index="0" type="array">
<numIndex index="0"><![CDATA[A value without comma]]></numIndex>
<numIndex index="1"><![CDATA[Hello World]]></numIndex>
<numIndex index="1" type="array">
<numIndex index="0"><![CDATA[A value with comma]]></numIndex>
<numIndex index="1"><![CDATA[Hello, World]]></numIndex>
<label>The Test</label>
(issue imported from #M7198)

Related issues

Related to TYPO3 Core - Bug #20021: Select doesn't allow comma in valueClosed2009-02-15


Updated by Christopher Schnell almost 13 years ago

As a workaround, you can use the char "Single Low Quotation Mark" that looks pretty like a comma. the HTML-Encoding is "& sbquo;" (without the space between the "&" and the "s" of course).


Updated by Tolleiv Nietsch almost 11 years ago

I'm sorry that's a TYPO3 Core issue with the TCEForm - I can confirm it for the latest TYPO3 trunk (4.4)


Updated by Stig Kjeldsen almost 11 years ago

Is there any patch for the bug or is it possible to solve it somehow?


Updated by Steffen Kamper almost 11 years ago

I already posted a patch for core, see #20021


Updated by Alexander Opitz over 7 years ago

  • Status changed from Accepted to Needs Feedback
  • Target version deleted (0)

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 7 years ago

  • Status changed from Needs Feedback to Closed
  • Is Regression set to No

No feedback for over 90 days.

Also available in: Atom PDF