Fields that are not localized should not be editable in the language that is not the primary one #13535
rolfsdMediaMarktSaturn
started this conversation in
Feature Requests & Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
When a field does not have localisation activated, its value can currently still be edited in the other language. If the content editor is not aware, he then mistakenly changes/ overwrites the language of the field, even though that's not what he wants. Please make it so that i can choose a primary language and all fields without localisation activated should not be editable in the secondary languages.
Beta Was this translation helpful? Give feedback.
All reactions