Issue Bug Closed

#83572Changed behaviour for uniqueInPid/unique in translated records

Jonas Renggli 01/15/18, 15:11 updated 12/23/19, 22:48

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

Reviews 4