The migration that happens when making a field translatable is fantastic. For content types using field translation, it just works. For content types that use node translation, existing values don't get converted properly.
Scenario:
- Blog content type, uses field translation (via Entity Translation)
- Article content type, uses node translation (via Translation)
- Field called field_workflow shared between Blog and Article
- Four languages enabled
Up until now field_workflow has not been translatable. Now we want to make it translatable and update lots of existing content. Although we would like to migrate Articles to use Entity Translation, we're not quite ready to do that yet.
Running "Enable translation" for field_workflow, checking the option for "Copy translations", everything works perfectly for Blogs. For the existing Articles, however, field_workflow appears to have no value when opening a node form.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | 1979406-4-entity-translation-values-not-filled.patch | 821 bytes | milesw |
| #4 | 1979406-4-entity-translation-values-not-filled.patch | 821 bytes | milesw |
| #1 | 1979406-1-entity-translation-values-not-filled.patch | 929 bytes | milesw |
Comments
Comment #1
milesw commentedWhat seems to be happening is that field_workflow still uses a language key of LANGUAGE_NONE. Since the field is now translatable, the language key needs to match the node language.
This patch allows field values to be re-keyed for node translations during the "Enable translation" process.
Comment #2
milesw commentedUpdating status.
Comment #4
milesw commentedOops, bad path in previous patch.
Comment #5
milesw commentedOops, bad path in previous patch.
Comment #6
plachLooks good and fixes the issue. Committed and pushed, thanks!
Comment #7.0
(not verified) commentedminor edit for clarity