When using cck content_multigroup and i18nsync, problems arise when creating translations because some nodereference fields can be null and need to remain null. But instead they are being disregarded.

For example, on my source node I have:


Content Multigroups:

noderef_field: (empty)
text_field: A

noderef_field: 1
text_field: B

noderef_field: (empty)
text_field: C

noderef_field: 2
text_field: D

When I create a synched translation I end up with:


Content Multigroups:

noderef_field: 1
text_field: A

noderef_field: 2
text_field: B

noderef_field: (empty)
text_field: C

noderef_field: (empty)
text_field: D

Because i18nsync_node_translation_nodereference_field() doesn't account for the empty node references, the deltas become incorrect and out of sync, putting the values into the wrong mulitgroup.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

sheise created an issue. See original summary.

sheise’s picture

Status: Active » Needs review
FileSize
888 bytes
joseph.olstad’s picture

Status: Needs review » Closed (outdated)
Related issues: +#419200: Interface language should not affect the node reference value

see my comment in:
#419200: Interface language should not affect the node reference value

in Drupal 7.x this is a configuration setting in /admin/config/regional/i18n/select
if you're wondering, the variable is called "i18n_select_nodes" , setting can be captured by 'features'

When referencing node types that have undergone entity_translation_upgrade or are already in ET (entity translation) mode, you'll want to NOT select by language, and the node reference field should be nontranslateable so uncheck this box