Problem/Motivation
Field translatability is defined at two levels:
- At field storage definition level it's defined whether the field supports translation and thus should have a storage supporting multilingual values.
- At field definition level it's defined whether the field is enabled for translation and thus actually be assigned multilingual values.
Currently the Field UI creates fields with untranslatable storage, which makes the Content Translation module simply ignore them, so they will never be translated as no UI to enable translation is exposed.
Proposed resolution
Make the Field UI create fields with multilingual storage by default, which is the same default we have in FieldStorageConfig, this way it will be possible to enable or disable translation later. Additionally clean-up the places that were not properly updated when introducing the split between field storage definition and field definition in the first place.
Remaining tasks
- Commit
User interface changes
None
API changes
None
Beta phase evaluation
| Issue category | Bug because field translation is broken for all fields created through the UI. |
|---|---|
| Issue priority | Critical because this severely reduces the content translation functionality for any entity type relying on the Field UI. |