Unique evaluation does not work with l10n_mode=exclude after editing original record again
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.
- File test_extension.zip added
- Complexity set to easy
- Sprint Focus set to On Location Sprint
I hacked a little extension to test the behaviour as an editor.
Create new language (if needed)
Create new Test element from extension
Create new translation of the page (if needed)
Open default language element
Hit save button.
Wrong behaviour: The value in the field will switch from "fieldvalue" to "fieldvalue0"
Correct behaviour: The value stays the same.