Related module: Internationalization 6.x-1.0-beta1

I've a content type (B) with a node reference field to another type (A). Both (A) and (B) are i18n-able (to set a node language). I follow these steps:

1) From italian path domain (I used domain instead prefixes), I create a (B) node with Italian as language. On nodereference list I see only nodes in Italian.
2) From the same path, I change language to English. I got no error screen, but now this English post contains references to (A) Italian nodes.
3) I change (B) node and I got a "this post can't be referenced" error.

Error message should be displayed on step 2, preventing to change language for this node if referenced nodes will not be referenced.

Comments

vladimir.dolgopolov’s picture

vladimir.dolgopolov commented

any news?

gaele’s picture

gaele commented
Project: Content Construction Kit (CCK) » Internationalization
Version: 6.x-2.0-rc4 » 6.x-1.0-beta1
Component: nodereference.module » Code
jose reyero’s picture

jose reyero commented
Title: this post can't be referenced after i18n language change » Node reference: allow cross referencing between different languages.
Category: bug » feature

I'm afraid this is a side-effect of how language selection works, it limits the available content for each language.

jose reyero’s picture

jose reyero commented
Status: Active » Closed (duplicate)

#314721: Node reference: results returned for interface language rather than node language

Anonymous’s picture

Anonymous (not verified) commented

Hello,

I would like to bump/refloat this issue as I am facing it right now.

This is a Spanish dictionary that uses CCK fields to define synonims that are called by means a node-autoreference. It has been done in Spanish and now I am translating the nodes into English. But when I try to add the translation, here comes the message about the reference that says "Sinónimos: este envío no se puede referenciar." (Synonims: This post cannot be referenced) (being a CCK field defined for Spanish).

However, I have found that I can avoid it by erasing the fields of Spanish synonims, making the English translation and afterwards, readding the synonims. Obviously, a real pain right there.

Otherwise, I can write another node, right in English, and then add it as a translation for an existing Spanish node.

So, there are some ways to bypass this.

However, the trouble persists with the CCK fields of synonims as, when I try to add them in the English version, I always get a message like this:

user warning: Duplicate entry 'nardo-es' for key 2 query: UPDATE url_alias SET src = 'node/567', dst = 'nardo', language = 'es' WHERE dst = 'nardo' in /home/coloquial/public_html/coloquialmente.com/modules/path/path.module on line 108.

    * Se han sincronizado la totalidad de las 0 traducciones de nodos.
    * Vocablo Nardo se ha creado.

If the short answer is 'this is so by design', next question is 'any plan to change it somehow in D7? If so, I would wait (I have no special hurry), if not, I would try to overcome it somehow.

Thank you.

Gustavo.