Repeatable: Always
1. Create a translatable node (with Entity Translation)
2. Translate the node in another language
3. Create a new link in a translatable menu with the path of the node (admin/structure/menu/manage/main-menu/add)
4. Translate this Link (admin/structure/menu/item/xxx/translate)
5. Go to the node - the link should be visible
6. Activate "Multilingual select"
6. Change the language to the translated version of the node
7. The Link is no longer visible

Expected Results:
The link is localized visible

Actual Results:
The link is not visible

Environment :
Drupal 7.10 (and 7.9)
Internationalization 7.x-1.x-dev (and 1.2)
Entity translation Alpha1

Comments

jose reyero’s picture

Category: bug » support
Status: Active » Closed (duplicate)

Multilingual select is somehow non-compatible with Entity Translation. ET nodes have a language so they may be filtered out depending on that language.

Anyway about ET compatibility please follow up here, #1182058: Add Entity Translation (entity_translation) support for menu items using Menu Translation

colan’s picture

Title: Translated Menu Link not visible when "Multilingual select" is activated » Menu item localizations to ET-translated nodes disappear with Multilingual Select module
Category: support » bug
Status: Closed (duplicate) » Active

This is not a duplicate as the above issue, now solved, does nothing to solve this problem. Localizations of a menu item linking to an Entity Translation node (one enabled with field translation instead of node translation) still do not show up in the non-default language while "Multilingual Select" is enabled.

So the workaround for now is to disable Multilingual Select, but we need to come up with a fix so that both can work at the same time.

jose reyero’s picture

Category: bug » support
Status: Active » Closed (won't fix)

Again, 'Multilingual select' is not compatible with ET nodes, see #1

This has been added to the documentation, http://drupal.org/node/1240340

Anyway, there are workarounds like disabling Multilingual select from specific pages (paths).

colan’s picture

Sounds like they're mutually exclusive. Thanks for the explanation.

kristen pol’s picture

Title: Menu item localizations to ET-translated nodes disappear with Multilingual Select module » Menu item localizations to entity-translated nodes disappear with Multilingual Select module (Entity translation compatibility)

Expanding title to allow for easier searching.

ressa’s picture

I have separate menus for each language, and when translating a node, the menu for the language to be translated to was missing all the children items. The full menu of the original language (english) was showing, but only the parent of the language to be translated to.

Disabling Multilingual select (i18n submodule) made the menu system work again, when translating nodes to another language, and display all children menu items.

parasolx’s picture

Number #6 solve my problem.

heretic381’s picture

Hi.
Is there a way to disable multilingual select per content type???

dimitriseng’s picture

Any answer to #8?

dimitriseng’s picture

Issue summary: View changes

updated formatting and some additional informations