i18n translation

Hey there,

As far as I know it does, I'm not quite confident though, but on the test sites I had everything worked fine even without that function.

This translation issue means that I cant use the menu item os a same view in a different languages?
Why you turned off the translation function?

This translation issue means that I cant use the menu item os a same view in a different languages?
Why you turned off the translation function?

Why was this function removed? It is hugely important for multinational sites. Thanks!

Hey all,

As a matter of fact, it was supposed to be a temporary removal, and only for the beta release, but then we ran into problems with the releases and I was forced to create a stable release; anyhow, on all test sites I had - like 3 or 4 - the i18n module was working like a charm, perhaps they changed the way i18n translates the menus, no gen, still busy and no chance to have a close look.

P.S.: You can add the function right after $cache['menu'] = menu_tree_all_data($menu_name); (D7: line #777, D6: #750)

  if (module_exists('i18nmenu')) {
    $cache['menu'] = i18nmenu_localize_tree($cache['menu']);
  }

Anyone else tried this?

When I injected the code as instructed, superfish menu just disapeared. It's possible I did something wrong.

This is what i did:

 else {
    $cache = array();
    $cache['menu'] = menu_tree_all_data($menu_name);
	
	//Translation (added)
	if (module_exists('i18nmenu')) {
    $cache['menu'] = i18nmenu_localize_tree($cache['menu']);
	}
	
    // For custom $menus and menus built all the way from the top-level we
    // don't need to "create" the specific sub-menu and we need to get the title

I'm using i18n and I have no problems with superfish. The way I did it was to include a menu link with each translation and adding it to the same menu as the nontranslated ones. You'll see in the menu just the links related to only a language. There is also a new handbook for i18n and maybe there is a better way, but this one is easy and works perfectly with no code changes.

Example:
-Menu
--News
---Sports
---Tech
--Noticias
---Deportes
---Tecnología
--Stories
--Historias

The correct code is:

    if (module_exists('i18nmenu')) {
      i18nmenu_localize_tree($cache['menu']);
    }

thank you kevinwal

It is working now! kudos!

I'm currently using Drupal 7.4 and Internationalization 7.x-1.0-rc1. Took me sometime to find out why the code in #6 and #10 are not working. The following code now works for me and hope it helped someone else with the same problem.

    if (module_exists('i18n_menu')) {
      $cache['menu'] = i18n_menu_localize_tree($cache['menu']);
    }

@turboflash thanks, works

I dont know if this is the correct thread but I will post here because it is concerning the i18n and superfish module.

I use superfish 7.x-1.8 and Internationalization 7.x-1.0-rc1 and I have a menu with "Translate and Localize"

The problem was that I was getting all language items for any language I choose at the language switcher.

Enabling the "Multilingual select" solved the problem without any code modification in the superfish module
(although I had another problem with Multilingual select see #1222244: Multilingual select Illegal choice )

The above code (#12 , etc ) when should be used?

Without that function custom menu items are not filtered for the current language, so all of them are shown regardless of the configured language, but menu items added from content nodes do. So I ended with some menu items showing in all supported languages and others showing only in the currently selected one.

Adding the removed language function back (#12) solved the issue for me.

If it cannot be added again, could we have a configuration option to enable it and avoid patching?

#12
Worked for me too...

Looking forward to see this in the next version of the module!

Thank you so much turboflash

Reagrds,
Ciril Tomy Tharayil
Tokyo, Japan

subscribe

subscribe

Thanks

The comment #12 worked for me.

The solution in #12 works for me with Drupal 7.8 and the latest i8n version. Can this be added to the next release?

As per #12 and reports above this patch has been tested by the community
please commit or create a dev for everyone to test

Hello, patch at #21 didn't apply. Here's proper patch.
Please test it and then mark as rtbc. Thanks.

Works and as per a few other reports above (22,21,20,19, 16,15,12) we all used #12 and report it to be working

lets move it to RTBC

Hey everybody,

Codes added back to the module (v1.9-beta3) thank you all :)

Hi ,

I experiment the same issue.... but where is this v1.9-beta3 version?

Thank you.

Mediator

You can find it at the following page
http://drupal.org/node/711944/release

It's still displaying all items in beta4. Will check the patch.

Patch from #22 worked.

I also confirm that version 1.9-beta3 works OK. Time to make it downloadable on the project page?

if menu item has "show as expanded" checked it is shown even with this patch

smartango
don't use patch use this version
http://drupal.org/node/711944/release

GiorgosK
I was using beta3, now beta4, same problem, only if "show as expanded" is checked.
Also, the weird part is that this check broke only menu links generated by taxonomy menu.
Currently I am using taxonomy menu to generate menu links, then I set language, and translate (i18n_menu) all links.

Also I am using entity translation for taxonomy, I would to add support for it in taxonony menu (or maybe make another module), but for the next project, I think end of July .. there should be something like translation support for menu then ..

Hi folks,

I still cannot make it work (7.x-1.9-beta4). Is superfish suppose to use translated menu items or you mean it can just provide a superfish menu block in a fixed language that visibility switch with?

It seems I cannot set the variable Title for translatable block. It remain greyed and if you submit without any variable set here you go with:

Notice: Undefined index: strings in i18n_string_translate_page_form_submit() (line 213 of E:\Web\Drupal_7\sites\all\modules\i18n\i18n_string\i18n_string.pages.inc).
Warning: Invalid argument supplied for foreach() in i18n_string_translate_page_form_submit() (line 213 of E:\Web\Drupal_7\sites\all\modules\i18n\i18n_string\i18n_string.pages.inc).

But I just found that the 7.x-1.8 with patch #22 does.

Cheers.

Confirming that #22 works for 7.x-1.8.

Since more people have confirmed this, perhaps it would be time to commit the fix.

Thank you

I was using Superfish 7x-1.8 before and had all, original and translated, menu items always visible in any language. I'm using i18n version 7x-1.7 too.

Installing version 7x-1.9-beta4 of Superfish, as said above, solved the problem for me.

Thanks!

@#25 richsky, I found that making sure to add a default language version first before you translate it gets around this error (at least in the block I was translating, for a Language chooser.)

Hello,

I've installed the version "7.x-1.x-dev" from 2013-Feb-08, it resolved me the issue !

Looks like this is fixed in the latest release.