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).
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | i18nmenu_node-905444-4.patch | 1.79 KB | plach |
| #1 | i18nmenu_node-905444-1.patch | 2.73 KB | plach |
Comments
Comment #1
plachThanks for reporting.
The attached patch should fix the issue (and remove old BC code).
Comment #2
plachComment #3
plachNew approach playing well with #879852-4: Menu item language is not set when adding a node with language set.
Comment #4
plachthe patch :)
Comment #5
plachCommitted to HEAD.