Goal: Referencing 2 corrsponding nodes of the same content type in an multilanguage environment with i18n and a synchronized node reference field across the languages, content negotiation is handled by the active translation module

Partially successful: Referencing works fine as long as both nodes have a translation. After creating the reference in the first node, I can edit the second and corresponding node and I will be presented with the right node reference in the widget. After saving the second node both have references to each other, as well as the translations of theses nodes, which was achieved by the synch option provided by i18n.

Problem: If the second node does NOT have a translation yet, the node reference field is pupulated with two references both to the first node AND its translation (I currently have two languages enabled). That causes that the node can not be saved because of an validation error (possibly invoked by i18n) and that I have to manually delete the reference entry that points to the "wrong" language node. Also somehow after saving I get an empty list entry in the list of the referenced nodes viewing the node.

Comments

domidc’s picture

Not sure cnr could do anything about this. Probably limiting the node to be referenced to just translated nodes? You could use a view to filter the nodes by language.

domidc’s picture

Status: Active » Postponed (maintainer needs more info)
Stolzenhain’s picture

Hello!
I have the same problem, but looking over the issue queues of i18nsynch, it seems more connected to this module.

Just for reference, here is my error message:

Reference overloading: [Title of Node] would of had 2 references and only 1 reference is permitted. Before adding a reference, you would need to edit [Title of Node] to remove an existing reference and resave this node to have make it correspond. Or you could allow this reference instance to have more references, go to the cck field settings of the instance

My problem is: To add my references, I use the Node Reference URL Widget which allows only for a single value in it's configuration.

After reading about all the complications in several module issue queues, I doubt there will ever be a solution for translation synchronisizing, but we should at least document the errors.