Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.While working on http://drupal.org/node/279333 I realised a fairly critical flaw in the plan - book module doesn't create hierarchies for book pages (or pages) by default - you have to go into the book fieldset, make a new book, and then it'll create the hierarchy - otherwise you just get a regular old page.
I haven't looked at the code which handles this fieldset yet, but assuming that other patch has legs, maybe we could hook_form_alter a #default_value into the 'page' node form so that it creates a hierarchy by default, and expands the fieldset by default. If that patch dies, it might still be worth doing this for 'book page'. this would bring things back somewhat to the D5 behaviour - where book pages were always in a hierarchy whatever happened.
Comments
Comment #1
Damien Tournoud CreditAttribution: Damien Tournoud commentedI came to the same conclusion while reading your other post. I'm not sure that the book module is the best candidate, thou. Why not simply forcing users to create a menu item for the page?
The idea I got was to add a new "Content type" parameter that would be "Force the creation of a menu item".
Comment #2
catchThat's another possible option - there's issues with that too though:
We already have main menu, secondary menu, navigation (which it'd be nice to separate out admin from my account/create content etc.). Main menu and secondary menu are displayed completely differently in different themes, and don't act like normal menus - no hierarchy for a start. We don't want new users adding stuff in navigation because it's too tied up with admin and hard to find stuff once it's in there. So none of them are currently good options for this task.
Started yet another issue to move admin out of the navigation menu, which would probably be a first step towards this. http://drupal.org/node/279399
Comment #3
Anonymous (not verified) CreditAttribution: Anonymous commentedI really like the Node Relativity module better than I like the current core book module. With it I can assign content types that are usable by the Node Relativity module and create a parent->child->grandchild relationship for any content type. Perhaps some of the concepts or even a the relativity module API could be used with the book module.
Book->Chapters->Pages->Sections->Sub-sections
Book is the only item that need be in the Navigation/Primary Links menu and then Book would contain the links to Chapters, the Chapters the links to Pages, etc.
Comment #4
btopro CreditAttribution: btopro commentedI've started to take a stab at overhauling book usability. It implements thickbox, books, and the new(ish) AJAX module to make 1 interface that you can quickly build ALL your site's content in. It's AHAH friendly and is making great progress! The project is called outline designer and any feedback would be appreciated. I really feel like this project could help improve the usability of the books module / drupal's hierarchy creation as a whole! There is a 5 version out but this demo is the D6 version to be released soon and blows 5 out of the water.
project: http://drupal.org/project/outline_designer
demo D6: http://elearning.vmhost.psu.edu/demos/outline_designer/
screencast of feature set: http://elearning.psu.edu/projects/files/D6_outline_designer_devcast.swf
Discussion / blog about the project: http://elearning.psu.edu/projects/node/124
6 Version in it's current state should be up as soon as I get around to creating a build, it's all ready to go for a dev / beta release but I need to get out of the pile of work i'm under. Hopefully up this weekend!
Comment #6
btopro CreditAttribution: btopro commentedD6 version of my Book Usability module was released, here's a working demo of the Release Candidate 2: https://elearning.psu.edu/demos/outline_designer/
Comment #7
kenorb CreditAttribution: kenorb commented#6 link is dead
Comment #8
btopro CreditAttribution: btopro commentedIt's working again now, sry bout that.
Comment #9
yoroy CreditAttribution: yoroy commentedOh hai!
Comment #10
sunComment #17
kenorb CreditAttribution: kenorb commentedComment #20
pameeela CreditAttribution: pameeela commentedWorkflow improvements sounds like a feature request rather than a bug. I'm sure this is still valid. Although, it's highly unlikely that Book module will get an overhaul in the year 2021 (or later!) but there has been increased activity on it lately.
Comment #25
quietone CreditAttribution: quietone at PreviousNext commentedThis extension is being deprecated, see #3376070: [Meta] Tasks to deprecate Book module. It will be removed from core and moved to a contrib project, #3376101: [11.x] [Meta] Tasks to remove Book.
This is now Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project and the Extensions approved for removal policies.
This issue may be re-opened if it can be considered critical, If unsure, re-open the issue and ask in a comment.