Display BookNavigationBlock when book root node is unpublished

I think the real issue here is that the original patch assumed that Published was the only way that access to a page would be managed. Of course, there are a ton of ways view access can be manipulated in Drupal, including Content Moderation, different permission levels, and access_alters. The patch at https://git.drupalcode.org/project/drupal/-/merge_requests/3279.diff accommodates those instead of just relying on the "status" column in the database. It should also not cause tests to fail.

Thank you for working on this!

Moving back to NW for the tests.

Previous tests passed and I've added a new one -- if that one passes I'll set to "Needs review".

Removing the needs tests as that was added to the MR.

But appears the test needs to be tweaked or the fix isn't correct.

This extension is being deprecated, see 🌱 [Meta] Tasks to deprecate Book module Active . It will be removed from core and moved to a contrib project, 📌 [11.x] [Meta] Tasks to remove Book Active .

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.

Isn't that correct Drupal though? If the parent is unpublished it's children shouldn't be available? MAYBE would accept as a configuration option if not a contrib module.

Actually just tested 2.0.x

Parent
- Child 1
--sub child1
--sub child2
- child 2

Placing a block in the sidebar region of Olivero
I unpublished parent and it still appears on all pages

unpublished child1 and block still appears for sub children

smustgrave → closed merge request !16