#95049Wrong default values of excluded localized fields
Description
If a BE user doesn’t have access to a field in a localized record, this field gets the default value upon save instead of the parent record value.
Use case:
Default language is Italian and a BE user must only translate (edit) secondary language Spanish. We want to simplify the experience of this user so we only display the title (header) and text (bodytext) fields of tt_content. With this bug instead is mandatory to enable all fields in “Allowed excludefields”.
Step to reproduce:
1. BE user can’t edit tt_content.header_layout of a localized tt_content record because is not selected in “Allowed excludefields”.
2. tt_content.header_layout value in parent record is 5.
3. BE user saves the localized tt_content record
Result:
Localized tt_content record have now value 2 (default value for header_layout) instead of parent record value 5.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Fix this issue
Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch
- Commit message
-
[BUGFIX] Wrong default values of excluded localized fields Resolves: #95049 Releases: main