Description of the need
We ran into this issue on backdropcms.org, where any node type can be classified as a book page, but then the book navigation shows up at the bottom of the page whether you want it there or not. It would be nice if we could provide a UI to control the placement of this navigation.
Proposed solution
Provide an interface to disable book navigation per node type.
* Use hook_fields_extra_fields() to allow book navigation to be disabled, or placed between fields. (Update: check the global setting for "Display default book navigation on book pages" and only show the per-node-type display option if that value is TRUE"
Draft of feature description for Press Release (1 paragraph at most)
Backdrop now includes the ability to hide or show book navigation per content type.
See https://github.com/backdrop/backdrop-issues/issues/3639 [META][UX] Improve book module.
Recent comments
For our DEV meeting: an older bug needs (and could have) a fix. Issue #5729 - Views: Search Filter: On Empty Input "Show None" option Shows All There are 2 pull requests, but one...
February 26th, 2026 - Weekly Meetings
Ruby Text can be a bit of a hassle to edit... Yes, I can imagine that. No idea, how an editor dialog (or whatever) for easier editing of those should look like - in terms of...
Specific tags to work in CKEditor 5
"why are these tags only relevant for admins?" I'm allowing the editor as well. That being said, Ruby Text can be a bit of a hassle to edit... easy to accidentally delete a tag or part of a...
Specific tags to work in CKEditor 5