Hello,

I made some tests with menu translation module and I noticed a bad behavior when the menu items are directly created from nodes.

Here is how to reproduce :

  • Define your menu as translatable
  • Create a content in one language, check the option to create a menu link.
  • Translate that content to another language, check the option to create the menu link too
  • Go to your menu, you can see that the 2 menu items have been created. If you check the language, you can see that each item have the same language than the node. This is the good point. But if you to to the translation tab for the menu item, you can see that the other item is not defined as translation. In other words, the 2 menu items are created but not defined as the translation of the other one.

I think this is a bug and the menu items should behave like the nodes. When you create a translation for a node and you setup a menu, the menu item should be the translation of the others menu item of the translated node, not just a menu item in another language without any kind of link between us.

What do you think about it ?

Regards,

Alex

Comments

Kaese’s picture

Kaese commented

I had a similar (the same?) problem just now and since I found a solution, I thought I'd share:

I had a site set up in one language and only when I added translations of the site, I installed Internationalization. So I had menus defined in a standard language, before I installed the menu translations module.

And when I translated the nodes and added the translated menu items in the process, it kept adding the menu items into the menus, not defining them as translations of the items in the standard language. I also noticed that it showed all menu items that I'd created before I installed the module as "language: undefined" even if the language of the connected node was defined (as the standard language). The translations of the node had "language: second language", though.

I guess the solution becomes obvious after this: You just go into old version of your node (the one in standard language), remove the hook for menu item, set the hook again (you don't even have to save, it doesn't save the information for some reason) and enter the information for the menu item again. That way the module registers the language you have set for that node.

I'd say it is still a bug that the module does not automatically define the menu item as the same language as the node, but at least this way you can make it work.

zmove’s picture

zmove commented

Any news about the issue ? It is officially confirmed and took into consideration ?

anni’s picture

anni commented
Priority: Normal » Critical

It doesn´t work at all.
In no language is the translated link (translated over node translation and adding menu link i node form) visible. Only the original link is there.
In the menu link administration form ere all links visible and enabled.

It seems like a critical bug.

jose reyero’s picture

jose reyero commented
Status: Active » Closed (duplicate)

See #1352218: Menu items don't relate to each other (sets) menu after creating translated versions