Fields that can't be translated, can be edited by translators in the entity translation UI. This results in inconsistent/confusing behaviour:

#2766957: Forward revisions + translation UI can result in forked draft revisions
#2861367: Field items lost on translations with empty values.
#2837022: Concurrently editing two translations of a node may result in data loss for non-translatable fields

Proposed resolution

Can we remove the ability to edit shared fields apart from in the original language of entities?

If not is there a way we can communicate this better?

Remaining tasks

User interface changes

API changes

Data model changes


catch created an issue. See original summary.

matsbla’s picture

Issue summary: View changes