Hi;
My problem is when i want edit a node in english but my node is in french, node reference is a english and no in french :s
I click on the content and I edit my article and this time there is no switch of the interface.
Have you a solution?
Thanks.
Comments
Comment #1
tomsm commentedI have the same problem:
Node references are updated between languages, but are not translated.
Comment #2
hass commentedNode references shouldn't be affected by translations as they are made with a NID and this NID is unique to a node of whatever language a node is - this shouldn't depend on the UI language.
Not sure what module you are using for node references and without this information there is no chance to help.
Comment #3
tomsm commentedThis problem has been solved now. But I do not know what fixed it.
Comment #5
dejavu1987 commentedUsing D7 and I m having same problem..
The problem is..
->We have a content in one language and using a node reference.
->When we try to edit the content from another language(not the language the node is in).
->The field using node reference gets a value from the node in the current language. (Not desired)
The only alternative to get through this is
->switch the language to the language in which the node is.(node that we want to edit)
->the field using node reference gets the correct value.
The feature that sounds missing here is
->the language should get switched to the language the node is in(The node that is to be edited)
regards Anil
Comment #6
Leeteq commentedIs this only relevant for 6.x, or also 7.x?
Comment #7
organicwire commentedI just reproduced the bug in D6. I have a multilingual node that can be of different languages. It has a couple of node reference fields which can link to nodes of different languages.
When viewing the node with a UI language different than the node's language, the node reference fields are not shown. This is an unexpected behaviour as the node references are given by their nid. So we should not not omit any nodes here.
The configurations that I tested:
- drupal 6.29
- i18n 6.x-1.10 (which is currently same as 6.x-1.x-dev)
- cck 6.x-2.9 or 6.x-2.x-dev
In my case, this unexpected behaviour was introduced with i18n 6.x-1.10 which fixed #614548.
Comment #8
joseph.olstadin 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
Comment #10
Anonymous (not verified) commentedOh man, I've been pulling my hair out for straight six hours trying to figure out why on earth I can't get all the translations show in an ET field. Can I buy you a beer joseph.olstad?
Comment #11
joseph.olstadGlad this helped, if buying a beer means thanks, then great!