Project

General

Profile

Actions

Feature #41773

closed

Add possibility to store NULL values

Added by Oliver Hader about 12 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2012-10-09
Due date:
% Done:

100%

Estimated time:
PHP Version:
5.3
Tags:
Complexity:
medium
Sprint Focus:

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 5 (0 open5 closed)

Related to TYPO3 Core - Bug #17624: can't set TCA field (and therefore db field) to NULLClosed2007-09-24

Actions
Related to TYPO3 Core - Bug #43139: Activating NULL value field does not work with blank stringClosedOliver Hader2012-11-20

Actions
Related to TYPO3 Core - Feature #43133: Integrate possibility to determine NULL values in TypoScriptClosedOliver Hader2012-11-20

Actions
Related to TYPO3 Core - Bug #43132: File Reference cannot be used to disable specific meta dataClosedOliver Hader2012-11-20

Actions
Related to TYPO3 Core - Bug #53662: DatabaseConnection INSERTquery does not allow NULL valuesClosed2013-11-15

Actions
Actions

Also available in: Atom PDF