I think the maximum number of levels deep a book can go is 9. In any event, I'm using the books module for a project that would require any number of levels deep, really endless levels. I know this would have consequences for multi-level book navigation, but I wouldn't be using more than one level of navigation on any page. Is there any way to override the number of levels limitation? Thanks for any help.

Comments

ainigma32’s picture

ainigma32 commented
Status: Active » Postponed (maintainer needs more info)

AFAIK this is the same limitation that is imposed on the menu depth.
See here #274270: Future of menu depth? for an issue where someone tried to increase that depth. There are also some recommendations for alternative solutions (i.e. use taxonomy)

Please post back how that works out for you.

- Arie

fumbling’s picture

fumbling commented

Thanks for the link. It looks to me like the suggested code, if it works, increases it to a given depth. What I need is no limit on depth. On the other hand, since I won't be showing any depth in any menu blocks, does it even matter? Will the book module continue to allow n-degree-child pages to be created ad infinitum? That's the gist of what I need. If this is purely a limitation on what displays in the menu that I'm fine. Do you know if it is?

ainigma32’s picture

ainigma32 commented

It's been a while. Guess this issue escaped my attention ;-)

Will the book module continue to allow n-degree-child pages to be created ad infinitum?

I don't think so. I think it will block creating child pages.

Or have you already proven me wrong?

In case you are still working on this I suggest you try asking on the developers mailing list or/and on IRC.

- Arie

fumbling’s picture

fumbling commented

you are right, at first I thought it didn't, but it does block those pages. In any event, I found that for what I was trying to do node-relativity or node-2-node modules made a bit more sense, as they don't have that limitation. Thanks for following up though, appreciate it.

ainigma32’s picture

ainigma32 commented
Status: Postponed (maintainer needs more info) » Fixed

No problem.
Since your original question was answered I'm setting this issue to fixed.

- Arie

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

natuk’s picture

natuk
Primary language English
Location Cymru
commented
Version: 6.9 » 7.x-dev
Category: support » feature
Status: Closed (fixed) » Active

Forgive me for re-opening this issue but I think it is important and it has not been looked at carefully.

In D5 there was no limit to the book generations. The limit introduced in D6 meant that upgrade was impossible for websites which require more than 9 generations for book nodes.

Node-relativity and node-2-node are heavy modules which people might not want to install for various reasons, plus they do not offer easy transition from the core book module.

If taxonomy is recommended for hierarchies in Drupal, then why keep the book module in the first place. On the other hand, if we accept that the book module is important to keep, then why limit it to 9 generations? And finally why 9 generations and not 10 or 100? It seems to me like an arbitrary limit.

Related discussions here:
http://drupal.org/node/274270
http://lists.drupal.org/pipermail/development/2009-February/031875.html
http://drupal.org/node/344019

I think it is reasonable to shift this limitation for D7 and allow a path for upgrade from D5 to D6 and D7.

- natuk

stephencamilo’s picture

stephencamilo commented
Issue summary: View changes
Status: Active » Closed (won't fix)
hestenet’s picture

hestenet
He/Him
Location Portland, OR 🇺🇸
commented
Status: Closed (won't fix) » Active

Reset issue status.

Status: Active » Closed (outdated)

Automatically closed because Drupal 7 security and bugfix support has ended as of 5 January 2025. If the issue verifiably applies to later versions, please reopen with details and update the version.