What, if any, is the correct protocol for rolling this module backwards? Were changes made to the database? Can I just turn the module off and upload the older version and turn it back on?

Since i have updated from beta6, all my nodes with references are unable to find nodes in a 2nd language, which is seriously screwing up my site. I have that part of it posted in the References issue queue, but so far there has been no response. I don't really know if the problem is on their side or with i18n. something apparently changed with i18n and References (which was relying on an uncommitted patch to get this working in the first place) didn't like it.

Comments

jose reyero’s picture

jose reyero commented
Status: Active » Closed (won't fix)

We may try to fix it, but investing any time on 'how to downgrade' is not an option. So if you want to reword this as a bug report...

cpelham’s picture

cpelham commented
Title: Is it possible to safely roll back from rc1 to beta6? » Since beta7, references module can no longer find references to translated nodes
Category: support » bug
Status: Closed (won't fix) » Active

Thanks, Jose.

I think the new title covers it. but to expand, If I edit a node that has a node reference field, and I want to reference a node in the primary language (in my case English), then the field form will find either the node title or nid and the node can be correctly saved and displayed.

However, if I try to reference a node (via title or nid) that is not in English, then I will get an error message saying that node cannot be found.

This worked under i18n beta6 (but only with the help of a patch that is in the References module issue queue but is not yet committed), but stopped working under beta7. So, this may be a problem with References. Maybe something in i18n changed and the patch to References needs to changea with it, but I am not sure.

jose reyero’s picture

jose reyero commented

This may be 'content selection'. Try disabling 'Multilingual select' module or disabling it for node edit paths.
node/add
node/*/edit

cpelham’s picture

cpelham commented

Disabling for those node edit paths solved the problem. You are a rock star, Jose!!

Can this be added into the install text file instructions? Or can it be disabled for those paths by default?

jose reyero’s picture

jose reyero commented
Category: bug » support
Status: Active » Fixed

http://drupal.org/node/1218844

Feel free to improve that instructions.

Status: Fixed » Closed (fixed)

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