Actions
Bug #83572
closedChanged behaviour for uniqueInPid/unique in translated records
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.
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
Actions