Hi,
There seems to be a big problem with i18n. I am creating a site with parent pages and child pages. I want to build the menu heirarchy in English (default language) then translate each of those pages. But when I translate a child page, the menu heirarchy is lost in the translated versions. Is it not possible to have ONE site tree, and translations of each page in that tree?
Thanks

Comments

sledgeman’s picture

sledgeman commented

Hi,
Similar problem here. We are trying to set up a very plain bilingual site, but for some reason things don't work out.
Here's our situation:
Drupal 6, i18n module installed. Three main navigation items (under 'primary links'), each with three sub navigation items.

First attempt: We translate each original Dutch page into French, using the built in 'Translate' option. We give each page a meaningfull (French) 'Menu Link Title' and choose either 'Primary links' (for main pages) or a french menu item (for sub pages) as 'parent item'.
So far so good. Everything works perfect. The content is being translated (we can use both language switcher at the top left of the screen, and the language switcher on the pages themselves) and the navigation structure is correct in both languages.
But from the moment we want to edit a French (translated) page, two strange things happen:

1. the (French) "Menu link title" that we had given to the translated page has mysteriously disappeared, and instead we see the Dutch 'Menu link title' that belongs to the original page.

2. the 'parent item' is no longer 'primary links' (for main pages) or a french menu item (for sub pages), but "Navigation".

As a consequence, simply opening the French pages for editing is enough to completely mess up the navigation structure.

(Our second attempt was to leave the 'menu link title' of our translated pages initially blank, assigning the link afterwards, through "site building/menu". That didn't work out either. Third attempt was to make a custom menu (in stead of using primary links), but exactly the same thing happened.)
We feel like we're out of options.

What is wrong?

Thanks!

brucepearson’s picture

brucepearson commented

see http://drupal.org/node/364375: Translated node forgets its menu settings

brucepearson’s picture

brucepearson commented

The module that we are currently developing to assist in translating Drupal sites works together with the i18n module and specifically handles the menu hierarchy. It works by creating separate menus for each language but makes sure the parent menus for a translated page point to the correct translated parent menu.

http://drupal.org/project/icanlocalize

It would be nice if the menu hierarchy was part of the i18nsync module so that the translated menu structure is duplicated and kept in sync with the original menu structure.

sledgeman’s picture

sledgeman commented
Status: Active » Closed (fixed)

Works!

Thanks a lot for this prompt and very useful feedback. Long live Drupal.

milos1234’s picture

milos1234 commented
Status: Closed (fixed) » Active

sorry, this doesnt solve the problem, so reopened.

let me try to explain a little further.

I create some pages in my site, some are Child Pages and Parent Pages. Then I go through and translate these pages one by one.

I start to translate all the top level pages, then translate the child pages. When adding a translation to a Child Page, the Parent Item of that page has to be redefined in the 'Menu Settings'. If you dont define the Parent Item of the translated node, then the translation of the Child Page is set to as the parent.

This is a huge usability problem.

What needs to happen is for i18n to recognise the parent of the child page i am translating.

The patch that brucepearson linked to http://drupal.org/node/364375#comment-1239318 only solves a different problem being this: If you edit a translation that already has a parent page, or menu setting, then those menu settings are forgotten.

Hope that makes sense.

kars-t’s picture

kars-t commented
Status: Active » Closed (cannot reproduce)

This issue is so old and I can't reproduce it. Feel free to open if this still applies.