Hi, I installed clean localizer module 1.7 on my 5.1 Drupal version with the pre-patched files to relpace the default ones in the install directory.

Every module component works fine (taxonomy, node, user, block) but don't work the menu localizer. I set the all own menu item's titles and descriprions in two localized language and when I change the language with locale switch block all content change, just the menu show the default english content.

I looked the localizertranslation table. I see the all titles and descriptions with right content, with right menu id and locale code.

What i don't do in right?

Thanks in advance

Comments

sun’s picture

Assigned: Unassigned » sun
Status: Active » Fixed

Please test the new Localizer version v2.x. Feel free to re-open this issue if it is not yet fixed.

jean-luc_rosier’s picture

Same problem here, should I update to the latest Dev release too ?
Anything to do before updating ? I'm new to Drupal...

Thanks

Roberto Gerola’s picture

Status: Fixed » Active

It seems to be a problem related to the cache.

Can you try to disable the cache support under performance and try again ?

Let me know.

jean-luc_rosier’s picture

Hi,
it starts to be really confusing, my cache is disabled, as I'm testing several things with this new installation of Drupal I don't want to have problems with cache, so it's disabled.
I gone into this today and tested with Firefox on the Mac as well as Firefox on my PC.
Results :

If I'm on the "Administer->Site Building->Menu" configuration page then some menu items translate and some not when clicking on the Language menu. If I'm on a regular page of the site and switch from one language to another it seems to work ! But... Even from a regular page I can't get the "Blog" Menu item to switch from one language to another !

Also I don't really understand why, while I have no checkbox selected into the "Select content languages", if I'm on a page (like the home page) with content translated, I get all translations and swithing from one language to another doesn't change this. I configured my "Super_admin" user to "When switching user interface locale, switch also the content locale" so switching from one language to another should also switch the content automatically and I should get other languages only when checking checkboxes in the "Select Content Languages" menu, don't you think so?

Hope my little tests help you to see what's going wrong...

Roberto Gerola’s picture

Are you using version 1.7, right ?

>Also I don't really understand why, while I have no checkbox selected into the "Select content languages",
>if I'm on a page (like the home page) with content translated, I get all translations and swithing from
>one language to another doesn't change this.

Disable for now the multilingual content support under Localizer preferences.

jean-luc_rosier’s picture

Hi,

yes I'm using Localizer v1.7.
I disabled "Multilangual support" but my "Blog" menu item doesn't change when I switch from one language to another.
All other menu items change but this one resist... hmmmm... Perhaps he doesn't like being translated ? :->

jean-luc_rosier’s picture

I deleted the Blog menu item and created a new one with translations and now...
:-) This one seems to not be so... hard-headed!
It woks now.

Do you think it's better to disable "Mulilangual support" ? Is there bugs with this ?
I find it very usefull because it allow people charged of translations to see immediatly which articles are translated and which ones are not.

Roberto Gerola’s picture

> I deleted the Blog menu item and created a new one with translations and now...
> :-) This one seems to not be so... hard-headed!
> It woks now.
Ok, clear now.

At now localizer trasnlates only the menu items that you have created and
not menu items provided by modules that should be translatable through localization
interface.
This behavior will change, so that it will consider also menu items created by other modules.

>Do you think it's better to disable "Mulilangual support" ? Is there bugs with this ?
No, it should work correctly.
I've asked you to disable only to be sure that this feature was not causing some confusing
in debugging your problem with the menu.

You can use it safely.

Thanks.

Roberto Gerola’s picture

Status: Active » Fixed

It should work in version 1.9.

Let me know.

Anonymous’s picture

Status: Fixed » Closed (fixed)