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.
I use book structure for an online course in a Drupal site. It would be useful if I could hava a checkbox to change the "publication options" from the admin/content/book menu, as I actually can change de order or edit de nodes.
Comment | File | Size | Author |
---|---|---|---|
#2 | 234509-publish_unpublish_admin_books.patch | 3.28 KB | Feng-Shui |
Comments
Comment #1
PasqualleComment #2
Feng-Shui CreditAttribution: Feng-Shui commentedThis is a bit of a tricky request. Controls can easily be dropped in on the book overview form to allow pages to be unpublished, but once a book page is unpublished, it is no longer appears on the overview form (as menu_tree_check_access removes unpublished nodes). As such, unpublished book pages can not be published via this form.
Solution 1: menu_tree_check_access could be copied into the book module and then altered to remove this check, although it would also have to bring along _menu_tree_check_access too, which brings along _menu_link_translate etc etc. Which isn't ideal.
Solution 2: Stick with unpublish only and and design the control to infer (as far as possible) a one way operation.
Would be interested in some input on this issue. At any rate, I've added a patch that would allow publishing and publishing if unpublished pages were shown.
Comment #3
mgiffordBumping this to D8
Comment #5
mgiffordAlso putting in a link to a related, possibly duplicate issue #26552: Allow users with access to unpublished nodes to create unpublished books
Comment #6
mgiffordThe book module needs some love...
Comment #9
Manuel Garcia CreditAttribution: Manuel Garcia as a volunteer and at Appnovation commentedLatest patch is for D7 so rather than a reroll what we need here is a brand new patch if you we want to see this on D8...
Comment #15
ptmkenny CreditAttribution: ptmkenny commentedClosing in favor of https://www.drupal.org/project/drupal/issues/372092 which is a more general issue for the same need. Since this issue only has a D7 patch, any commit to core will have to start with a D9 patch at this point.
Comment #16
ptmkenny CreditAttribution: ptmkenny commented