The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Hi,
we setup a page with translatable content. The main content is a large book (~ 400 pages).
The main content is english and we translated it into 4 languages. Using your module it was easy. :-)
Then we wanted translateable menus so we activated the i18n_menu and i18n_select modules. After some fiddeling with their ui we were able to translate our menus aswell.
But now we have to add another language translation and that works for non-book pages but not for the book. :-(
If we click on the translate link the interface has changed which we noticed first. And after we save the translated page we get an error messages which is repeated every time you visit the page (see screenshot 1).
Notice: Undefined index: link in menu_tree_output() (Line 1019 in /www/iforest/includes/menu.inc).
Notice: Undefined index: link in menu_tree_output() (Line 1019 in /www/iforest/includes/menu.inc).
Notice: Undefined index: link in menu_tree_output() (Line 1019 in /www/iforest/includes/menu.inc).
Notice: Undefined index: link in menu_tree_output() (Line 1019 in /www/iforest/includes/menu.inc).
Furthermore the i18n_book block shows not the correct content (see screenshots 2 and 3) and if you click on the translated link to the translated book page the menu gets messed up even more (screenshot 4).
I tried to disable the i18n_menu and i18n_select modules but that did not work out.
Do you have any ideas or ran into a similar issue?
Regards,
Jens
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | screenshot5.png | 35.17 KB | telematika |
| Screenshot 4 - broken menu (german) | 10.26 KB | telematika | |
| Screenshot 3 - missing/broken menu (german) | 9.97 KB | telematika | |
| Screenshot 2 - correct menu (english) | 17.74 KB | telematika | |
| Screenshot 1 - Error message | 65.46 KB | telematika |
Comments
Comment #1
wadmiraal commentedNo, I've never ran into this kind of problem. But it does seem worrying.
What do you mean by:
You mean the "translate" tab on a node page ?
And if you disable i18n_select and i18n_menu and clear all caches ? Is it still broken ?
Kind regards
Comment #2
telematika commentedHi,
yes, our translater said that after enabling the i18n_menu and _select modules the interface changed a bit.
I guess she refers to the lower part where you can now select the translation for the current node.
I disabled the select, menu and block translation modules and cleared all caches. The problem still persists. :-(
I'll try some more and keep you informed.
Regards,
Jens
Comment #3
telematika commentedHi,
so far I have been able to reproduce the problem.
1. create drupal site and enable only i18n_book_navigation
2. add languages to the site
3. create a book with multiple pages
4. translate the book using i18n_book_navigation
5. enable the other i18n modules
6. add another language
7. click translate on a book page and choose the new language
8. click save... boom... :-(
If I enable the other i18n modules (menu etc.) together with i18n_book_navigation right from the start the error does not occur.
However I got another one instead but only a warning (see screenshot).
So I guess this is some kind of side effect/race condition that occurs if you enable other i18n modules later on. My guess is somewhat in the direction of the strings module, because that one did throw an error 2 times during the activation in my test runs.
Regards,
Jens
Comment #4
wadmiraal commentedThank you for the information.
I'm very busy at the moment, but I'll get to it as soon as possible.
I'm not very familiar yet with the new i18n_* modules. They've changed a lot compared to D6 and when porting it to D7 I was afraid it might clash with some other i18n module... turns out I was right...
Comment #5
wadmiraal commentedOk, working on it now :-). Stay tuned.
W
Comment #6
wadmiraal commentedI can't reproduce the error.
I used the latest i18n 7.x-1.7 and variable 7.x-2.1 and I did not get any errors (except the Notice on #3, that's fixed on latest 7.x-2.x).
I followed your steps exactly on a clean install, but nothing happened.
Which versions are you using ? And if you use previous versions, did you try to upgrade (don't forget to backup !!) ?
Kind regards,
W
Comment #7
wadmiraal commentedComment #8
telematika commentedI was using i18n module 7.x-1.5. Currently I'm trying to upgrade the whole site to the latest modules and will report back if the problem gets solved.
Comment #9
telematika commentedOkay, using the latest i18n module (1.7) the error is gone! :-)
Comment #10
wadmiraal commentedGreat, thank you !
Comment #11
Gib... commentedHi,
Just updated to Drupal 7.16, all modules up-to-date.
We had book translation problems in the navigation block so I found about i18n Book Navigation.
Installed version 7.x-2.1 and now I get :
Notice : Undefined index: link dans menu_tree_output() (ligne 1019 dans /home/.../public_html/includes/menu.inc).
Did not find what is "i18n_select module" anywhere on Drupal.org. Might be "Multilingual select". When I disable that module, the above notice disappear but all nodes show up on a page whatever the language.
Any click on a node link gives :
Fatal error: Call to undefined function i18n_get_lang() in /home/.../public_html/sites/all/modules/i18n_book_navigation/i18n_book_navigation.module on line 823.
Installed version 7.x.2.1-dev. Same result.
I removed all translations of book pages, so all book pages are only in one specified language (not neutral). Same result
Comment #12
wadmiraal commented@Gib
Can you tell me how to reproduce the Notice ?
The second point (Fatal Error) you mention is discussed here: #1797612: Call to undefined function i18n_get_lang(). It's corrected on 7.x-2.2.
Comment #13
wadmiraal commentedOk, the error remained and I found out why. It is fixed on dev.