Hi,

I just downloaded CA module and installed it successfully on drupal 6.22. This is the only module I have installed. When I am browsing a page whose content type is set to Anonymous and Authenticated (ie: boxes checked under "View any content type"), I don't have access to see the page when I am either logged in as a user or I am at the page anonymously. If only one of the two fields is checked for the content type of the page I am visiting, the page is visible to the user type whose view any content box is checked. Am I doing something wrong or is this a bug?

Comments

good_man’s picture

good_man commented

"If only one of the two fields is checked for the content type of the page I am visiting"

Can you explain what are these two fields?

jetatar’s picture

jetatar commented

Let's say that I create a new 'Page' type content. The 'Access Control' settings of content 'Page' has several permission options, ie:

"View any page content":
- Anonymous User
- Authenticated User

If the boxes for both Anonymous User and Authenticated User are checked simultaneously, neither an anonymous user nor an authenticated user have permission to view the page created. If only one of the fields is checked (either Anonymous User OR Authenticated User) then that user group does indeed have access to the page.

I have pages which I want both an anonymous and an authenticated user to have access to. How do I do that?

Thank you.

good_man’s picture

good_man commented

I did exactly what you said, and it's working. Are you sure this issue is not from another module?

jetatar’s picture

jetatar commented

I am confident. I make a new clean install of drupal 6.22 and the latest CA release version of 6.x-1.x-dev. I can provide you with admin login access to the clean install so you can verify.

Thank you very much again.

good_man’s picture

good_man commented

Can you install devel module and enable devel access submodule and give access of the dev information to auth. and anon. and then post back the devel access block results (devel access displays access info on a block in footer region)?

jetatar’s picture

jetatar commented

This is what I see on the front page when I am logged in as admin.

node_access entries for nodes shown on this page

node realm gid view update delete explained
Welcome content_access_all 0 1 0 0
Bubbles content_access_all 0 1 0 0
Wel content_access_all 0 1 0 0
asdf content_access_all 0 1 0 0

There are several pages which I know are promoted to front page status, and the page types are such that anon as well as auth. should be able to see, but as soon as I log out from admin, I get the welcome page I would see right after installation has been completed (as if I have not promoted my own front page).

Here is a link to the site with the installation:
https://atlasweb.ps.uci.edu/~arianna/drupal-6.22/

richH’s picture

richH commented
Version: 6.x-1.2 » 6.x-1.x-dev
Priority: Normal » Major

Hi,

I have exactly the same problem on D6. I've installed Content Access and ACL both of which are 6.x-1.x-dev. As admin I can see everything, but the anonymous user cannot see a thing. Only when I uncheck the access to a content type for authenticated users, can the Anonymous user see the content types.

Rich

jetatar’s picture

jetatar commented

Yep. Same here.

oriolo76’s picture

oriolo76 commented

On D7 disabling the Content Access module allows accessing from anyone, but of course this is not a solution.
Still waiting for a very important patch.

oriolo76’s picture

oriolo76 commented

here it is:
http://drupal.org/node/1213148

MichaelCole’s picture

MichaelCole commented
Priority: Major » Critical
MichaelCole’s picture

MichaelCole commented
Priority: Critical » Major
good_man’s picture

good_man commented

Commit reverted, please test it and tell me if it's fixed.

good_man’s picture

good_man commented
Status: Active » Needs review
Todd Young’s picture

Todd Young commented

Is this yet rolled into a DEV release?

gapple’s picture

gapple
he/they
Primary language English
commented
Status: Needs review » Closed (duplicate)

This issue was caused by a commit for #239139: Do not hijack the 'all' realm, which has since been reverted and should be resolved by updating your module to the latest dev version.