Hello,

Since upgrade of i18n 1.6, it seems not support the menu item Translate and Localize.
"Translate and Localize. Menu items with language will allow translations. Menu items without language will be localized. "

Related issue in i18n is #1658748: Menu links associated to a node with a language different to the current language are not hidden anymore., and it seems will never be fixed.

So here is the patch who have changed the translate method from menu item to multi menus with different fixed language.

The patch will let superfish to choose the right menu to display.

CommentFileSizeAuthor
i18n-menu-variable-translate.patch857 byteswqmeng
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Jose Reyero’s picture

I don't understand at all the purpose of this patch, since you can have different menus per language (on the same variable) with i18n.

Anyway about the node links in the menu #1675830: How to use i18n_menu_localize_tree (or other) to hide menu items from other languages

wqmeng’s picture

Superfish only get the english main menu to display. before i18n 1.6 the funcation i18n_menu_localize_tree will get the English main menu to be localized. After i18n 1.6, many user now use fixed language and create main menu for each language. In this case, superfish still use the English main menu, and i18n_menu_localize_tree will not localize it anymore As the Menu menu not have any localize menu items anymore.

With this patch, it will let superfish to use Main Menu for English and Main Menu CN for Chinese, Main Menu DE for Germany.

Jose Reyero’s picture

The only thing that has changed in i18n 1.6 is that node menu items are not filtered out using node access anymore. So you need to use i18n_menu_localize_tree to get your menu items filtered out by language and localized.

Multilingual / localized menus are working as they were before and i18n_menu_localize_tree should still be working. So we should be able to localize superfish menus using i18n_menu_localize_tree, which Superfish 1.9-beta4 does.

If not maybe there's a bug we should fix on i18n?

About the menus / variables yes, I see the problem which I think is superfish using variables to store block settings and multilingual variables not supporting such thing.

mmind1’s picture

Thanks, the patch works great to combine Variables Translation for internationalized menus and the Superfish module!

-mmind1

MXT’s picture

Jose Reyero said:

About the menus / variables yes, I see the problem which I think is superfish using variables to store block settings and multilingual variables not supporting such thing.

On the above, Please Jose, I would like to receive your think about http://drupal.org/node/1849272

Thank you very much

cmseasy’s picture

Multilingual select menu filter, part of the Internationalization contributions module, http://drupal.org/project/i18n_contrib, solved this for me.

mehrpadin’s picture

Issue summary: View changes
Status: Needs review » Closed (works as designed)