Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I have installed and rebuilt permissions etc.
Tested many times.
Does seem to work for anonymous as expected.
Does NOT work for authenticated user
Comments
Comment #1
shunshifu commentedI just had the same experience.
However I was using a book created from a different content type other than a book page. When I use an actual book page to create a book it works.
Phil
Comment #2
webel commentedAha, that could well explain it, I am also using content types other than book throughout my hierarchy, although the top-level node of each book is always a BookPage. Well done Detective Phil. I'll do some tests and reports back.
Comment #3
shunshifu commentedGlad to be of service
Phil
Comment #4
avpadernoThis is not a bug, but it's the way the module works.
The module works only for the book content type, not for other content types. Even if you create book pages from nodes of different content type, the content type of those nodes is not changed to book page.
Comment #5
harry slaughtersee http://drupal.org/node/350805
Comment #6
webel commentedHi Kiam,
Thanks for confirming this.
This needs to be documented clearly right at the top of the install and online documentation,
because it is a security/access matter and very easily overlooked or inadvertently assumed.
Q: Could it not be possible to extend the system to handle any node participating in a book ?
The current behavior severely restricts the utility of this otherwise very useful module.
Webel
Comment #7
avpadernoSee the reply given in #350805: Book Access seems to have no effect; the module code has been changed so that it can handle every content type used like book page.