I have a site with three books. Each book has its special access rules. See screenshot access_adipositas_rolle.png, access_beyourself_rolle.png and access_gfg_rolle.png.
A user e.g. Frank Herzog has role access to the roles adipositas and beyourself, see screenshot user_frankherzog.png.
When frank logs in, he sees only the book with the right permissions, screenshot before_adding_page.png. But as soon frank adds a child page to a book, he has access to the book gfg, to which he has no access.
Using now 2.0-alpha5 version and Drupal 6.20.
I had this problem with the 1.0-rc6 version in Drupal 6.19, thats why I tried the 2.0-alpha5 version and Drupal 6.20. Same in alpha4 and Drupal 6.19.
Any ideas? Help is appreciated.
Thank you.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | snapshot1.png | 63.78 KB | Anonymous (not verified) |
| after_adding_page.png | 40.21 KB | chiefkong | |
| before_adding_page.png | 26.82 KB | chiefkong | |
| user_frankherzog.png | 48.92 KB | chiefkong | |
| access_gfg_rolle.png | 48.11 KB | chiefkong |
Comments
Comment #1
chiefkong commentedComment #2
Anonymous (not verified) commentedI fixed the reference to a local variable used by a function, and tested the module; I could not reproduce the issue.
I created a new official release (http://drupal.org/node/1007312); please test it, and report here if it works for you. Remember to update the access permissions before, and after installing the latest official version.
Comment #3
chiefkong commentedHello kiam,
thank you for your prompt help. Unfortunately, the new version alpha 6 did not solve the problem. I certainly did update the access permissions before and after updating the new version.
BTW, I did notice: The books, frank has no access to, which are showing up after creating a new book page, disappear after updating the content access permissions.
But as soon as frank creates an new book page, the other not permitted books appear again.
I allready tried to update the content access permissions via an action right after some user creates new content, but coundn't find the appropriate action module.
So, thank you again for your help. If you need any further information to get the problem solved, let me know.
Comment #4
Anonymous (not verified) commentedDo you have any other node access control modules?
I created three different roles, and three different books which were accessible from each of the roles; I then created a user account with two roles, and when I logged in with that account, I was not able to see the book associated with the third role, even after creating a book page.
Comment #5
chiefkong commentedNo, I don't.
To get closer, I set up a complete new site only with the drupal 6.20 core, Administration menu 6.x-1.6 and Book access 6.x-1.0-rc6.
I set up three books, three roles and a user frank, who belongs to two roles. Stell the same problem.
You can see it under test.projektgruppe-21.de.
I will mail you an acount, where you can see it by yourself.
Comment #6
Anonymous (not verified) commentedThank you for helping out with the issue.
I tried logged in as frank and created a test page in Project01 book; I assigned the book to the page, and clicked on the Save button. The screenshot show what I get after.
I will keep testing to try understand when the issue comes out, exactly.
Comment #7
Anonymous (not verified) commentedI have noticed that the test site is using version 6.x-1.0-rc6, while this report is opened for version 6.x-2.0-alpha5.
The test on my test site has been done on the latest development snapshot for branch 2.x, and I didn't verify the issue; it could simply mean the issue has been resolved on the branch I am testing on my own computer.
I will have to expand the SimpleTest tests to include a more complete test (as in the case shown in the this report).
Comment #8
chiefkong commentedUpps,
sorry, my fault. I set up the test site with the wrong version of the book access module.
Now I did set up the site completely new with the right version of book access (6.x-2.0-alpha6).
And I did set up the same users (frank and kiam) with the same passwords – it ist still not working.
Try to log in as frank (frank has acces to the project books 01 and 02) and create a new book page. You should see immediatley the project_03, which should not to be.
Comment #9
Anonymous (not verified) commentedI think I found the cause of the issue reported in this report. The module created a row in the node_access table that cointained a value for nid equal to 0; that happened when the book page was created, and the node object passed to the form submission handler didn't contain a valid value for the node ID (I assumed Book access would execute its own submission handler after Drupal set the node ID).
I also fixed other bugs I found, which caused the Add child page to appear when it should not.
Please test the development snapshot when it will be available the new archive. I tested it in my test site, and it worked.
Comment #10
Anonymous (not verified) commented@chiefkong: The new development snapshot has an update function that removes the spurious entries created in the node access table; remember to execute the updates, before to test the module.
Thank you again for your help with this issue.
Comment #11
chiefkong commentedkiam,
ah, I got it – and it works!! Great!
I installed the development snapshot on the test site as well as on my production site, and I can confirm, that no longer not permitted books get visible after creating new book pages.
So, thank you very much. I appreciate you fast help very much.
Thank you again, and I'm looking forward for a stable release for this great and helpful module.
Comment #12
Anonymous (not verified) commentedI will create a new official release between two days.