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.
i have a multilingual website with books. sliced book navigation does not allow me to have blocks for the same book in language A and language B. either blocks for book in language A or blocks for book in language B. which is obviously a critical problem for such a useful module...
(tested in drupal 5.3)
Comment | File | Size | Author |
---|---|---|---|
#3 | slicedbook_navigation-5.x-2.0-i18n.patch | 1.09 KB | marcus_clements |
Comments
Comment #1
vthirteen CreditAttribution: vthirteen commentedalwex, the module author, replied:
"The solution I actually use for multilingual site based on a book is to make a
tree including each langages I need.
if your first branch subdivise your site in multiple langages, you don't need to
use a multilingual module.
It was the first benefit I was looking for with sliced book navigation
And never forget, "one book to rule them all" !
Comment #2
vthirteen CreditAttribution: vthirteen commented[issue status changed]
Comment #3
marcus_clements CreditAttribution: marcus_clements commentedWhen you add translations using i18n the new nodes created are added into the book tree and are all shown in the slicedbook_navigation blocks.
This patch detects the language of each node in the tree and will not add nodes with a different language.
If no language is specified by the node they are added to the tree.
This is helpful because when a partially translated book is displayed the untranslated nodes in the default language are still displayed.
Hope this helps someone.
cheers
marcus
Comment #4
marcus_clements CreditAttribution: marcus_clements commentedThe patch above is useless actually.
I should have read the posts above properly...