Posted by kenjil on April 27, 2011 at 10:59am
8 followers
| Project: | Book access |
| Version: | 6.x-1.0-rc8 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs review |
Issue Summary
I've installed book access, but even if i reconstruct access rights, it's still doesn't work.
Amongst other thing :
Even though a role was not given edit permission on a book, it can still access and edit some (sic !) of its child.
Either there are some missing instructions which omit to tell what's this module is really doing
or this module is completely buggy.
It's a shame since the idea was promising.
Comments
#1
Hi have the same issue. I have configured the settings for my book on the Book Access tab, so that anonymous users should not be a
able to view book. However, anonymous users can still view the child book pages. It only seems to have restricted access to the top-level book page.
EDIT:
I just rebuilt permissions again at /admin/content/node-settings and it works fine now. Seems one needs to do this several times.
#2
Wanted to use this module because I have multiple books in a website and need to control access.
For me, it's the view permissions that aren't working at all.
I have 13 books. I started to configure the books so that different roles can edit and that anon and authenticated users can view.
I've only configured 3 books so far but everyone can still see all the books, even though I haven't finished the permissions yet.
#3
6.x-1.0-rc8 does nothing on my site. There is a comment in one issue that Book Access cannot provide access if another module denies access. This is the reverse. Nothing is denying access.
I rebuilt permissions three times and the permissions did not change. I cleared the cache. No change.
I tried to find the section of code where Book Access gives access to roles and did not succeed. Image Gallery Access is installed and does exactly the same thing for image galleries as Book Access is supposed to do for books. Image Gallery Access works.
This problem combines with a book module problem, where you cannot create an unpublished book, to make book publishing unusable. I will have to write the books outside of Drupal and only add to Drupal when finished. Perhaps I can delete the Book Access module and use workflow or a node access module to restrict access to pages that are not ready for publishing.
#4
Update: flush cache, have no other access modules in place, set your permissions correctly and success.
#5
For me it's not working as expected. When I change access rights with this module, it has no effect on documents. It works only after visiting admin/content/node-settings.
#6
I am having this same issue on D7 branch
#7
I think the problem is, that by default, when the access rebuild is done, if there is no custom grants (to users or roles), drupal core adds by default to node_access a row like this
nid, realm, view, update, delete ....
111,all,1,0,0,...
meaning that node 111, as view granted on all realm
I dont know what would be the right way, but i expected that, after installing this module, NO user would have view permission (or any other) to my site books.
Hope any developer can give us a little help on this.
#8
BTW, My issue is on v7.x
#9
I think this patch should solve most problems.
Hope some module developer give me a review?
BTW, the patch is for 7.x.2.x branch
#10
I think this patch should solve most problems.
Hope some module developer give me a review?
BTW, the patch is for 7.x.2.x branch
#11