Very simple fix to annoying problem with the book module. Once you assign a non-book page as a top-level book page (through outline), you can't make it stop being a book.

Simple fix/patch included.

CommentFileSizeAuthor
book_no_remove.patch576 bytesmoonray
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm commented
Version: 5.x-dev » 6.x-dev
Status: Needs review » Reviewed & tested by the community

Committed to 5.

ax’s picture

ax CreditAttribution: ax commented

shouldn't this be committed to HEAD, too?

Dries’s picture

Dries CreditAttribution: Dries commented
Status: Reviewed & tested by the community » Fixed

Committed now! Thanks.

Anonymous’s picture

(not verified) CreditAttribution: commented
Status: Fixed » Closed (fixed)
ashledombos’s picture

ashledombos CreditAttribution: ashledombos commented

sorry for this old topic coming back but is this patch still necessary to remove top level node from book ?

regards

bohmann’s picture

bohmann CreditAttribution: bohmann commented

Yes, the patch is still necessary (v6.16). A (not so pretty) alternative to the patch is to open database table "book" and delete the row that holds the node-book relation - that worked for me (not recommend for production sites).