Project

General

Profile

Actions
Copy link

Bug #83572

closed

Changed behaviour for uniqueInPid/unique in translated records

Added by Jonas Renggli over 6 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
DataHandler aka TCEmain
Target version:
-
Start date:
2018-01-15
Due date:
% Done:

100%

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

Description

Starting with TYPO3 8 LTS the behaviour for TCA's uniqueInPid/unique setting has changed when used in a field exluded from translation.
In our extension we're using a field with a technical key that needs to be equal independent of the language used.

Actual behavior
Translated field values get a numeric suffix. E.g.
  • myvalue
  • myvalue0
  • myvalue1
  • ...
    This suffix is not visible in the backend as the field is excluded from translations but considered in the frontend.

Expected behavior
Translated field values excluded from translation ('l10n_mode' => 'exclude') shouldn't be altered.

Steps to reproducs

  • TCA 
    'key' => [
    ...
    'l10n_mode' => 'exclude',
    'config' => [
        'type' => 'input',
        'size' => 40,
        'eval' => 'uniqueInPid',
    ],
],
  • Create element in default language
  • Translate this element to another language
  • Check in frontend or database for altered values

Related issues 3 (0 open — 3 closed)

Related to TYPO3 Core - Bug #87038: Unique evaluation does not work with l10n_mode=exclude after editing original record againClosedBenni Mack2018-11-29

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

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

Actions
Actions
Copy link

Also available in: Atom PDF