Problem/Motivation

When we create a new translation for an atom, the fields marked as translatable are not been populated with the source language values.

Steps to reproduce

Tested on SimplyTest.me with the Scald Galaxy distribution + the entity translation module.

1) Enable the locale and entity_translation modules.
2) Add a new language like french [/admin/config/regional/language]
3) Make atoms a translatable entities [/admin/config/regional/entity_translation]
4) Unchecked the "Hide language selector" for one of the bundle. We tested with the image bundle.
5) Create and attach a new field [field_scald_subtile] to one of the atom bundle [admin/structure/scald/image/fields]
6) Create a new atom item and fill in the translatable field [field_scald_subtile].
7) Create a translation
8) The translatable field [field_scald_subtile] is not pre populated ;(

Proposed resolution

When the fields are attached we can pass along the $langcode.

Remaining tasks

Review patch

User interface changes

None

API changes

None

CommentFileSizeAuthor
#2 translatable_fields_not_prepopulated-2391369-2.patch664 bytestargoo

Comments

targoo’s picture

targoo commented
Issue summary: View changes
targoo’s picture

targoo commented
Version: 7.x-1.2 » 7.x-1.x-dev
StatusFileSize
new translatable_fields_not_prepopulated-2391369-2.patch664 bytes

Patch tested on 7.x-1.x-dev and 7.x-1.2

nagy.balint’s picture

nagy.balint commented
Status: Active » Needs review
nagy.balint’s picture

nagy.balint commented

Seems to be working fine, Thanks for the clear reproduction steps.

nagy.balint’s picture

nagy.balint commented
Status: Needs review » Fixed

Thanks! Committed.

  • nagy.balint committed 3e9b145 on 7.x-1.x authored by targoo 
    Issue #2391369 by targoo: Translatable fields are not populated with the...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.