#87038Unique evaluation does not work with l10n_mode=exclude after editing original record again
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
Reviews 2
Related issues 4
- Bug #83572Changed behaviour for uniqueInPid/unique in translated records
- Bug #84267Unique evaluation does not work with l10n_mode=exclude
- Bug #90653TCA eval with uniqueInPid: allow identical value in localized content
- Bug #93817TCA unique evaluation fails for unchanged value in default language with l10n_mode=exclude