Project

General

Profile

Actions

Bug #84267

closed

Unique evaluation does not work with l10n_mode=exclude

Added by Christoph Lehmann about 6 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Must have
Assignee:
Category:
Localization
Target version:
-
Start date:
2018-03-14
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
8
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Translation handling changed 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 “fieldvalue1”.

My expected behaviour is: uniqueness is ignored for translated records, since the values are just copied.


Related issues 5 (1 open4 closed)

Related to TYPO3 Core - Task #86780: Add test for (wrong) unique eval handling in pages:aliasClosedBenni Mack2018-10-28

Actions
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 #87038: Unique evaluation does not work with l10n_mode=exclude after editing original record againClosedBenni Mack2018-11-29

Actions
Is duplicate of TYPO3 Core - Bug #83572: Changed behaviour for uniqueInPid/unique in translated recordsClosed2018-01-15

Actions
Has duplicate TYPO3 Core - Bug #84666: Page alias is changed for translated pagesClosed2018-04-08

Actions
Actions

Also available in: Atom PDF