I have added 5 book pages into my book, each node has a parent book node referenced in it's book settings. On admin/content/book/N (where you go to re-order the book pages) there are only three items in the list, in spite of there being five nodes in the book.
To reproduce:
1) create three book nodes, in succession, placing each into the book using the fields on the node.
2) navigate to the book_admin_edit page and save an order.
3) create some more book nodes, placing each into the book using the fields on the node.
4) navigate to the book_admin_edit page again. You'll notice your new book nodes are missing.
may or may not be related to #26552: Allow users with access to unpublished nodes to create unpublished books
Comment | File | Size | Author |
---|---|---|---|
#8 | drupal-book_cache_issue-1936908-8.patch | 1.76 KB | Sivaji_Ganesh_Jojodae |
#5 | drupal-book_cache_issue-1936908-5.patch | 1.77 KB | jamiehollern |
#2 | drupal-book_cache_issue-1936908-2.patch | 1.71 KB | jamiehollern |
book-outline-busted.png | 50.26 KB | jenlampton |
Comments
Comment #1
jamiehollernLooking at this during the code sprint (25th January 2014).
Comment #2
jamiehollernThis was an issue with an out of date cache. The book admin page data is saved as a menu and utilises the menu cache once the admin page is viewed for the first time. Clearing the menu cache fixes this issue, however this cache was not refreshed/deleted when a book node was created/updated/deleted*. The patch I've added deletes the cache when a node is added/updated/deleted.
* When a node was deleted it appeared to update, however this was simply cosmetic as the node no longer existed. The menu item still existed in the menu cache entry.
Edit to say thanks to Paul Linney for his help with this issue.
Comment #5
jamiehollernUpdated patch.
Comment #6
jamiehollernComment #7
jhedstromNeeds a reroll, and there are trailing whitespace issues in the patch above.
Comment #8
Sivaji_Ganesh_Jojodae CreditAttribution: Sivaji_Ganesh_Jojodae commentedStraight re-roll of patch #5.
Comment #10
mgiffordJust unassigning so someone else can take this on.
Comment #11
jamiehollernI can no longer reproduce this bug.