i18n 1.6 was just released. Installed but it appears to break i18nmenu_node.

Not sure of the exact reason yet, but downgrading to i18n 1.5 fixes the problem.

Here's the debugging I've done so far; maybe it'll help someone figure out what's up and whether the problem is with i18n or i18nmenu_node.

using i18n 1.6:
In i18nmenu_node_menu_link_alter, $item['language'] is set to the default language when creating or resaving a language specific node and even when switching the node from a language to language neutral. The result is that $item['options']['translations'] doesn't get set, and any translations you create will create their own menu items (instead of allowing you to translate the original menu item).

Comments

plach’s picture

Category: bug » task
Priority: Normal » Major
Status: Active » Needs review
StatusFileSize
new2.73 KB

Thanks for reporting.

The attached patch should fix the issue (and remove old BC code).

plach’s picture

Title: i18n 1.6 breaks i18nmenu_node (use 1.5 instead for now) » Make i18nmenu_node work with i18n 1.6
plach’s picture

plach’s picture

Version: 6.x-1.0-alpha3 » 6.x-1.x-dev
StatusFileSize
new1.79 KB

the patch :)

plach’s picture

Status: Needs review » Fixed

Committed to HEAD.

Status: Fixed » Closed (fixed)

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