Hello!

In case we use Main menu in 'Translate and Localize' mode, all translations of particular item will be shown as independent items, simultaneously. Presumably this is because Kanji, instead of using the normal menu links, pre-filtered according to language, fetches the links data from the Drupal menu system itself (to implement drop-down menus maybe?).

To reproduce this bug, you need 'Menu translation' module (from Internationalization 7.x-1.0 package) enabled. But Kanji shouldn't implement any Internationalization - specific code to solve this problem; for example, core Bartik theme shows only one translation at the time, not all of them.

CommentFileSizeAuthor
#4 kanji.zip459.07 KBDonnyCarette
#3 kanji.zip459.07 KBDonnyCarette
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

DonnyCarette’s picture

Assigned: Unassigned » DonnyCarette

Reproduced the error and indeed the issue comes from the drop-down menu's.
Thanks for pointing out, i'm surprised that nobody else has mentioned that issue before :-)

I'll look for another way to pull the menu items, so the dropdown stays

DonnyCarette’s picture

The only way so far seems to replace the menu by a region and place the menu inside that region on the blocks page.
I will look if there's no other solution, but could not find something so far

DonnyCarette’s picture

FileSize
459.07 KB

Hi Renat,

You can use this attached new version of the theme, i added a new region 'main_menu' where you can drop your menu.
If there's nothing inside the region the normal primary menu will be used. Maybe this is a better way, now people can also use other menu's or modules to place instead of the main menu.
(Clear cache after updating)
Can you let me know if everything is fine?

DonnyCarette’s picture

FileSize
459.07 KB

Duplicate (First comment did not appear wright away)

renat’s picture

Hi, Donny!

Theme from #4 works perfectly fine. In case you place main menu in a new region, there appears only translated items, in case you remove this menu from that region, everything returns to initial situation - just as you expected. In case I'll notice any problems later, I'll inform you, of course.

I completely agree, that idea to put Main menu in special region is, probably, best option here. Before starting this issue, I studied similar bugs for other themes - it's maintainers didn't find any silver bullet to solve this problem.

And yes, thank you for such a quick response - I thought it'll take much more time!

DonnyCarette’s picture

I will do more testing this week, but i don't expect any more problems with this version.
Probably it would be better to always use the region for menu's and skip the primary menu inside page.tpl, but i don't want to confuse other people that are using this theme allready for a long time :-)
Next week or so, i'll add a new release with this changes and add a message on the project page about this changes.
Thanks for reporting this issue ;-)

DonnyCarette’s picture

Status: Active » Closed (fixed)

New release 7.x-1.7 added based on the zip file of comment #4
(Closing)