[TYPO3-mvc] Blank Flexform fields overwrite TypoScript values???
Bastian Waidelich
bastian at typo3.org
Fri Feb 26 12:06:38 CET 2010
Martin Kutschker wrote:
Hi Masi,
> Maybe these cases are rare, but I've stumbled upon this problem before.
I don't think, those cases are rare.
Imagine a custom suffix you want to set to an empty string in your
flexform. Or a float field to enter the tax amount. There is no way to
distinguish between 0.00 and NULL.
It would be a neat feature to enable optional flex form fields that you
could remove resulting in a NULL (or not set) value.
For extbase we went the safe way for now: If a flexform field exists, it
overrides the corresponding TS setup no matter what.
If you have a better idea shoot, but "($flexFormValue !== '') {
$settings[$key] = $flexFormValue)" is not an option for the reason above..
Bastian
More information about the TYPO3-project-typo3v4mvc
mailing list