Bug #87038

Updated by Alexander Bohndorf 6 months ago

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

Back