Working on unpublished books messes up book hierarchy of other book

Hi
I too facing same problem. Currently i am using Drupal version 7.15, Once i unpublished book and the subpages become members of the very first book and also book hierarchy also changed. I tested in drupal 8.x-dev, but same issue created. Please check this issue

With regards
tssarun

Based on the report, should be major.

I'm not entirely certain if this issue is identical to #26552, but fixing #26552 should also solve this issue.

This issue (#1688026) specifically refers to top level nodes in a book outline that are unpublished. When the top level node is unpublished, it disappears from the book outline menu, but the usual first menu item on the book outline menu "create new book" is not displayed so when you make any edits to the the top level book node, it gets reassigned against the first book that appears after the "create new book" selection option on the Node Edit form. From this point, the original book item is gone even if you republish the top level book node. The top level node, which was previously a book of its own is now a child node and all of its children are also adopted into the new top level book node parent. If you look at the book table in the database, everything under that book ID is now missing.

At this point, your original hierarchy appears to be irreversibly wrecked, but so long as you don't make any edits to any of your original child nodes, all you need to do to get Drupal back to normal is to republish your original top level node while at the same time selecting "create new book" in the Book outline at the same time. Now, I just said that "create new book" is not an option anymore, but it reappears once your node is assigned against a parent after your first edit. Once you save your node as a new book, it then gets re-created as a top level book node and once it becomes a top level node again, it carries all of its child relationships out from under the incorrect parent. I know this sounds confusing so I'm going to show some steps to reproduce this at the end of this entry.

This will only work if you don't make any edits to the child nodes underneath your original top level node while it's unpublished. Doing so will cause your child nodes to get reassigned against another top level node. If there are no other top level nodes, then the node you're editing will become a top level node itself when you edit it.

The hack to the book module suggested in #26552 works for D7 as well as for D8. In D7, if you comment out one database condition, the unpublished book node does not disappear from the book outline menu from the node edit form and so the relationships aren't broken when you save the form.

In D7, the condition to comment out is located around line 393

Steps to Reproduce

1. On a fresh system, create a book page named "Book A" and make it a new book.
2. Add one child page named "Child A" to the Book A hierarchy.
3. Create a book page named "Book B" and make it a new book.
4. Add one child page named "Child B" to the Book B hierarchy.
5. Unpublish Book B.
6. Edit Book B and save it, but before you hit the save button, look at the Book Outline options and notice that "Book A" is your only available option.
7. Republish Book B. Both Book B and Child B now belong to Book A.
8. Unpublish Book B.
9. Edit Book B. Go to the Book Outline and choose "create new book".
10. Make sure "published" is checked in the publish options.
11. Save Book B.

The original Book B hierarchy should be restored now and Child B is back under Book B.

Restoring version.

Hi

This issue is related to Allow users with administer nodes perm. to create unpublished books. , so i feel this issue duplicate.....

regards
tssarun

This issue is a duplicate because the other issue resolves this one as well. Please see #26552: Allow users with administer nodes perm. to create unpublished books..