Does it possible to make this?

Since I found that it only allowed me to assign one node to one book block. The feature request maybe consider to change from drop down select instead of multi-select option box.

Since right now, current code would load Ajax when one book is select to find if there any child books in one parent.

i 'm not sure if this feature can be done using Advanced Taxonomy Block, but if good if this feature can be include in next release version.

Comments

siliconmeadow’s picture

Hi,

As far as I know the book module is the restricting factor - the book module extends nodes, but only allows a node to belong to one book.

The book module is part of core, so you would need to log a feature request there. However, don't log a request there, as I just checked for you - this has been requested many times in the past, so it would be a marked as a duplicate. The sad news is, it would appear that it's not likely to be feature until Drupal 8, if at all. See:

http://drupal.org/project/issues/drupal?text=multiple+books&status=All&p...

I feel your pain though, as I could really use the ability to assign a node to multiple books too!

Cheers,

Richard

parasolx’s picture

Priority: Normal » Minor
Status: Active » Closed (won't fix)

After I review all the issue, it make me thinking twice about one node, multiple books. If this feature implement, i would confuse user. It make user see a couple of page that have identical content with previous one.

Also i think the main reason is to avoid duplicate content that would lead to decrease the SEO. So I'll mark this as closed and won't fix. Sorry about this.

Thanks

Webrotta’s picture

Another example:

We have a software that is a bit customer dependant so one manouver might go a bit different from customer to customer. Therefore we need to make different nodes for each cases to avoid one node to be too complex. Some manouvers are similar. So now the problem is that when we put a node to one book it cannot be referenced to another book. So i am basicly speaking of making customer relevant manuals.

I really think that this is something that should be fixed.

Sorry about poor english.