I have installed Content Access 1.1 and ACL 1.4 on Drupal 5.2. I have also allowed per-node access control for a given content type.
So, for each of these nodes, I have an 'Access Control' tab with two sections (the first one concerning the roles, the second one about users (ACL module).

The problem is that, if I try to allow access to a role (for example 'authenticated users'), it no longer works (it's working properly without the ACL module). Apprently, the 'user' section seems to override the 'roles' sections, which would then logically lead to this denied access as I set nobody in the 'user' section. But, if the behaviour is the right one, it seems quite illogical, I would have thought that both kind of access were cumulative such that you can gives access to roles AND specific users and not having user-based priviledges superseed the role-based ones.

Can anyone light my fire on that behaviour ? At least, to able able to tag this as a 'bug report' or a 'by design' tag.

Comments

fago’s picture

fago
Primary language German
Location Vienna
commented

hm, for me it's working fine together.
Just a guess: Have you changed the content access priority? ACL doesn't support this yet, which could cause these problems.

marquardt’s picture

marquardt commented

Hello,

I experience precisely the same problem (with v1.2). If ACL is enabled, a fresh node is initially visible to anonymous users. However, as soon as I modify the settings in the role access settings, and without changing the user specific ones, the node disappears for
the anonymous users.

Christian.

marquardt’s picture

marquardt commented

Sorry - I forgot to mention that I didn't touch the content access priority option; it still has it's default post-install setting.

fat-eddie’s picture

fat-eddie commented

I'm having the same problem. Specifically:

1. Create a page. Very simple just a title and text.
2. Page content type has per node access control settings enabled.
3. Page content type has default settings of View: anonymous user and View: authenticated user
4. Anonymous user can see the page fine.
5. Administrator goes to the page and clicks on "Access Control". Permissions are as expected View for anonymous and authenticated.
6. Click "update" - doesn't matter whether any changes have been made to the privs or not.
7. Access is then denied to any user who doesn't have "Administer Nodes" privs for Page content.
8. The node that was created has gone from table node_access. This is confirmed when using the development module by running a "Node Access Summary" report which comes back with: "You have 9 nodes in your node table which are not represented in your node_access table. If you have an access control module installed, these nodes may be hidden from all users. This could be caused by publishing nodes before enabling the access control module. If this is the case, manually updating each node should add it to the node_access table and fix the problem."
9. Rebuilding the permissions under Post Settings doesn't fix the problem.
10. Neither does the suggestion from the development module - changing / resubmitting the node doesn't put it back in the node_access table.

No taxonomy running for me - just:
// $Id: content_access.module,v 1.1.2.3 2007/05/19 16:40:41 fago Exp $
// $Id: acl.module,v 1.1.2.11 2007/05/18 13:23:49 fago Exp $
// $Id: node.module,v 1.776.2.1 2007/01/29 21:51:53 drumm Exp $

Scratching head..
Eddie

fat-eddie’s picture

fat-eddie commented

Actually, the bit about taxonomy module not running is a lie - it is but only because the forum module insisted on it - so not doing any kind of access stuff that I'm aware of.

marquardt’s picture

marquardt commented
Version: 5.x-1.1 » 5.x-1.2

Hmm,

I've played a bit... In the role access control settings, there's also an author role which, in the default configuration, isn't ticked for any of the operations. I have ticked the author checkboxes for view, update and delete - and voila, anonymous users can see the nodes again...

Devel tells me that each node now has two entries in the node_access table for the realm 'content_access_rid', and a third one for 'content_access_author'. Is that the way it's supposed to be? I've tried to read the code, but I only understand some of what's going on there...

BTW, I think http://drupal.org/node/169991 and maybe http://drupal.org/node/158271 are duplicates of this one.

fago’s picture

fago
Primary language German
Location Vienna
commented

yes, that sounds right. What entries are there, if you don't tick the author permission?

marquardt’s picture

marquardt commented

For me, the default settings in the access control tab for each content type immediately after the installation of the module were view rights for anonymous and authenticated users, and nothing else. In particular, the author had neither view, edit or delete rights.

If enabling autor rights did indeed solve the problem - why would author rights affect rights for anonymous users???

fago’s picture

fago
Primary language German
Location Vienna
commented

It shouldn't.

Can you please test it again and tell me which grants are written in both cases?
I assume in your access control settings you have anonymous users "access content" but they have no permission to "edit content" or "edit own content"? (this settings affect the grants, that are written)

deviantintegral’s picture

deviantintegral commented

I've been having a similar problem.

If I edit an existing node, it will become inaccessabile to all but node administrators. If I then resubmit the Access Control page, everything works as expected. As well, if I disable the ACL module without resubmitting the Access Control page, everything works.

Let me know if there's anything I can do to help. I'll try and do some work on this later this week.

--Andrew

talktozee’s picture

talktozee commented

I am having similar problems with: Drupal 5.2, ACL 5.x-1.4, and Content Access 5.x-1.2.

If I turn off the ACL module, then everything works like it did before I installed anything. Re-enabling it breaks anonymous and authenticated access of existing nodes that have had ACLs applied to it, even if I Rebuild Permissions or re-submit the Access Control page.

Thoughts?

jfall’s picture

jfall commented

I've got the same problem id'ed above - will track this issue in hopes of solution.
Does anyone know the difference between this Content Access module and the NodeAccess (http://drupal.org/project/nodeaccess) module?
Both appear to do very similar (identical?) things... After trying both, I settled on this one because NodeAccess is in dev. for 5.x ...
Anyone got a reason to pick one over the other?
Thanks.

harriska2’s picture

harriska2 commented

Ah, thank you jfall. I looked and had NodeAccess installed. With it installed Content_Access didn't work. I uninstalled NodeAccess and it now works.

Thanks!

internets’s picture

internets commented

I'm having similar issues using Drupal 5.2.
I have ACL 5.x-1.4 and content_access5.x-1.2

I have pages / content
Setup a role for 'editor'

I installed the ACL and Contact Access modules, didn't change any settings for any of my already created pages. I created a test page to make sure it was working. My goal was to have ' editor ' create a page, make it private, visible to 'editors' and one specific user. This seemed to work well.

As 'editor' I edited the home page content. The home page became inaccessible to anonymous users. I resubmit the access control default settings. It did not work.
Tried disabling / re-enabling the module.

Now if I edit a page as an admin or 'editor' the page becomes inaccessible to anonymous users, If I go to the access control tab and re-submit the settings the page is visible to anon users.

It would be nice if the page stayed visible to anon users after editing the page without having to re-submit the accesss controls.

fago’s picture

fago
Primary language German
Location Vienna
commented
Status: Active » Closed (duplicate)

http://drupal.org/node/169991