Feature #41773
Add possibility to store NULL values
| Status: | Resolved | Start date: | 2012-10-09 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | - | % Done: | 100% |
|
| Category: | Backend User Interface | Spent time: | - | |
| Target version: | - | |||
| PHP Version: | 5.3 | Sprint Focus: | ||
| Complexity: | medium |
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',
...
);
Related issues
Associated revisions
[FEATURE] 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.
This feature is enabled by adding "null" to the eval list of
the TCA configuration of a field, example:
'columns' => array(
'title' => array(
'config' => array(
'type' => 'text',
'eval' => 'null',
)
)
)
Besides that, of course the database field definition needs to
be updated to support NULL values.
Change-Id: Ib5cd0e34e34d084df7ba3380ae81e5240bcf76d6
Resolves: #41773
Releases: 6.0
Reviewed-on: http://review.typo3.org/15458
Reviewed-by: Oliver Hader
Tested-by: Oliver Hader
History
#1 Updated by Gerrit Code Review almost 3 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
#2 Updated by Gerrit Code Review over 2 years ago
Patch set 2 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/15458
#3 Updated by Gerrit Code Review over 2 years ago
Patch set 3 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/15458
#4 Updated by Gerrit Code Review over 2 years ago
Patch set 4 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/15458
#5 Updated by Oliver Hader over 2 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 9f1efb64de1df113e944fd7bd34b87504c402c57.
#6 Updated by Klaus Hinum about 2 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?
#7 Updated by Ernesto Baschny almost 2 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.