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)

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

vthirteen’s picture

alwex, 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.

     -- French   -- Fr site structure

BOOK -- English  -- En site structure

     -- Spanish  -- Es site structure

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" !

vthirteen’s picture

Status: Active » Closed (works as designed)

[issue status changed]

marcus_clements’s picture

Status: Closed (works as designed) » Needs review
FileSize
1.09 KB

When 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

marcus_clements’s picture

The patch above is useless actually.

I should have read the posts above properly...