Add possibility to store NULL values
The current implementation in the TYPO3 backend does not allow to store NULL values, only empty strings or zero as number are allowed.
Since the overlay behavior of FAL takes e.g. the description property from the original file object an empty value in the disposal (the referenced file) cannot be defined to be blank, thus not clearing the original file description.
For this case we need a new behavior to allow NULL values in the storage and to handle that in the backend view.
For this a new TCA
eval property needs to be created
'config' = array(
'type' => 'input',
'eval' => 'null',
Updated by Ernesto Baschny over 7 years ago
- Target version deleted (
Hi Klaus. When you enable "eval=>null" you will get a new checkbox besides your input field. The field is only "activated" once this checkbox is clicked (thus allowing to store the "empty string"). Once you click the checkbox, the field is disabled (and NULL is stored in the DB).
I noticed that the position of this checkbox is a bit bogus (at least in the current master), I opened up an issue to get that fixed (#52261).
Does that explain the feature to you and why the field is disabled at first? Probably you didn't notice the new checkbox.