Project

General

Profile

Actions

Bug #87038

closed

Unique evaluation does not work with l10n_mode=exclude after editing original record again

Added by Alexander Bohndorf almost 6 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Must have
Assignee:
Category:
DataHandler aka TCEmain
Target version:
-
Start date:
2018-11-29
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
9
PHP Version:
7.2
Tags:
Complexity:
easy
Is Regression:
Sprint Focus:

Description

Translation handling with l10n_mode=exclude:
the field is copied from default language to language children. In combination with eval=unique the language children get a unique value too like “fieldvalue”.
If you edit and save the original record afterwards then "fieldvalue" turns into "fieldvalue0" because the uniqueness is also checked in translated records.
My expected behaviour is: uniqueness should be ignored for fields with l10n_mode=exclude in translated records.

Related to #84267
Related to #83572


Files

test_extension.zip (4.67 KB) test_extension.zip Jan Helke, 2018-12-07 11:33

Related issues 4 (1 open3 closed)

Related to TYPO3 Core - Bug #90653: TCA eval with uniqueInPid: allow identical value in localized contentNeeds Feedback2020-03-05

Actions
Related to TYPO3 Core - Bug #84267: Unique evaluation does not work with l10n_mode=excludeClosedOliver Hader2018-03-14

Actions
Related to TYPO3 Core - Bug #83572: Changed behaviour for uniqueInPid/unique in translated recordsClosed2018-01-15

Actions
Related to TYPO3 Core - Bug #93817: TCA unique evaluation fails for unchanged value in default language with l10n_mode=excludeClosed2021-03-25

Actions
Actions

Also available in: Atom PDF