Currently Display Suite hijacks the book navigation field and uses the book navigation block to return the output.

The block module provides separate theming functions, templates and preprocesses for a book navigation inside a node and book navigation inside a block, these are:

For displaying navigation in a block, renders only the table of contents, and uses Render API.

For displaying within a node, prints the table of contents and a book pager with next, previous and top level links.

So Display Suite breaks sites that rely on the book module because the next, previous and top level links are no longer shown on the node page.

Why is this important?
If, for example, page switched to a display suite layout, the "‹ Devel up Install Display Suite ›" links at the bottom of the page would no longer be shown (and there'd be no clean way of getting them in as the block on the right hand column would have to be overridden as well).

Patch attached that fixes this.

Members fund testing for the Drupal project. Drupal Association Learn more


codesidekick’s picture

Status: Needs review » Postponed

Need to double check DS configuration on a clean Drupal install - turns out the site I was given was messed with to invoke the book navigation block.

swentel’s picture

Status: Postponed » Closed (works as designed)

No comments or new updates from others for a while, closing.

webservant316’s picture

Issue summary: View changes

Continuing discussion here since this ticket is closed.