Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
By Robert Broen on
Hi Everybody,
In our new multilingual site, all nodes/pages show up in the main_menu, this is not funny on a site with 60 pages and 5 languages.
The nodes translate nicely and remain connected (which is really nice).
It would be even better if I could filter the menu items base on a language. Doe anyone have a notion how to solve this?
I am reading Kristen's e-book, but have not found this problem tackled (yet).
My setup: Drupal 7.14 with i18n module (except field-translation, I'm going for node-translation)
For the 'Page' content type my settings are...
Publishing options -> Multilingual support -> Enabled, with translation
Menu settings -> Extended language support is set to: Normal - All enabled languages will be allowed.
For the 'Main-Menu' my settings are...
Translation mode -> Translate and Localize. Menu items with language will allow translations. Menu items without language will be localized.
Thank you for helping!
Comments
I am having the same problem!
I really don't understand why is this. I am trying to rebuild our bi-lingual site using drupal. But for the moment all items in the main menu show up (meaning two "Home", two "About us", two everything. I looked a lot in the documentation and I tried many things. Please, help!
The same here
When we built the menu, everything worked fine, German menu items appeared when the language was set to German with either browser preference or URL, and the same for Turkish.
Now all menu items in both languages are displayed always, no matter which language you choose with the language switcher, by URL or browser. I have no clue if we changed a setting that triggered this behaviour or if this is just a bug that occurs.
Besides I miss the content language detection on /admin/config/regional/language/configure, which was available before afaik, and it still is on my local test site.
Well this issue was posted a
Well this issue was posted a long ago. i don't know what solution was found by the people here who had the problem. In any case in my case it was a bug in the theme I was using. I fixed it easily with one line of code.