Feature #41773
closed
Add possibility to store NULL values
100%
Description
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 null, e.g.
'config' = array(
'type' => 'input',
'eval' => 'null',
...
);
Updated by Gerrit Code Review about 12 years ago
- Status changed from New to Under Review
Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/15458
Updated by Gerrit Code Review about 12 years ago
Patch set 2 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/15458
Updated by Gerrit Code Review about 12 years ago
Patch set 3 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/15458
Updated by Gerrit Code Review about 12 years ago
Patch set 4 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/15458
Updated by Oliver Hader about 12 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 9f1efb64de1df113e944fd7bd34b87504c402c57.
Updated by Klaus Hinum over 11 years ago
As soon as I add "eval" => "null" the field is not editable in the backend any more. Is there a missing setting or is this on purpose? How can I edit the field then?
Updated by Ernesto Baschny about 11 years ago
- Target version deleted (
6.0.0-RC1)
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.
Updated by