Bug #70421
closed
displayCond IN operator doesn't work like documented
100%
Description
In CMS < 7.5 it was possible to set up a displayCond against a select field and using the IN operator. For example 'displayCond' => 'FIELD:doktype:IN:20,24‘,
Currently this condition is always evaluated to false, because values of select fields are now handled as arrays by form engine.
Updated by Gerrit Code Review over 8 years ago
- Status changed from In Progress to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/43837
Updated by Sebastian Iffland over 8 years ago
Thomas Maroschik wrote:
In CMS < 7.5 it was possible to set up a displayCond against a select field and using the IN operator. For example
'displayCond' => 'FIELD:doktype:IN:20,24‘,Currently this condition is always evaluated to false, because values of select fields are now handled as arrays by form engine.
The greater than ('>') comparison seems to fail too, see field 'l10n_parent' (also type select) in any table. It appears even if language set to -1 [All] or 0 default.
Updated by Vladimir Falcon over 8 years ago
I confirm the error mentioned by Thomas.
l10n_parent Field is always visible regarding of the sys_language_uid.
'l10n_parent' => array(
'displayCond' => 'FIELD:sys_language_uid:>:0',
'exclude' => 1,
'label' => 'LLL:EXT:lang/locallang_general.xlf:LGL.l18n_parent',
...
),
Updated by Thomas Maroschik over 8 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 037ca4187dc464820bc5d0aa4653de6faac68b77.
Updated by