Anonymous user cannot see a Content Profile Node [#1056200]

Hi there

I have a few a content profiles on my site. I've created a view of all content profile types and various fields from that profile. As an authenticated user, I can see the view list.

As an anonymous user, I am unable to see the list.

I've even given anonymous users permissions to access user profile > but still nothing.

Is there any place where I may set permissions for the content profile, or could there be a node access conflict?

Other modules on the site: taxonomny access (but this should have no effect)
And then:
site_user_list > with this module, Anon users can see the content profiles, but we are unable to sort it the way we want to - hence we wanted to create a view of all content profiles.

Any suggestions.

I'm using Drupal 6.20.

I've just seen: The 6.x-1.3 release of Taxonomy Access Control fixes a major bug where editing nodes under certain conditions would corrupt node access records, possibly leading to restricted nodes being accessible. >> Could this maybe the cause?

Comments

Comment #1

boon4376 commented 21 June 2011 at 20:32

I am having this problem as well.

I have content profile and the advanced profile kit setup in order to create a "staff" section of our website.

Our staff members all have their own profiles and I want anonymous users to be able to see them. I have setup a view which displays a list of all staff members or "profiles". However, when an anonymous user actually visits the profile at, for example "users/mrideout" they are greeted with

Access denied
You are not authorized to access this page.

I need anonymous users to be able to view profiles. I have checked all relevant boxes inside the permissions area, I do not know what would be causing anonymous users to now be able to view profiles.

Please Help. Thanks.

Comment #2

smithmilner commented 19 September 2011 at 18:27

I'm having this problem too, I've found rebuilding the site permissions will fix the issue temporarily but I haven't found the source. I don't have taxonomy access installed so that's not the issue here.

Comment #3

smithmilner commented 19 September 2011 at 22:06

I have fixed the issue I had with this. I found that profile nodes were simply not being included in the node_access table, the moment I added entries for them they worked perfectly. The problem was not with the module itself but was closely related. I was using the option to embed the profile node into the user profile page. Because of this I was looking to forward users from the profile node to the user profile page using an drupal_goto() in a hook_nodeapi call. This at the very least disrupted the "insert" operation of that hook and the node_save function was never completed. The very next line in the function was to add node_access entries for the node, figures :P

http://api.drupal.org/api/drupal/modules--node--node.module/function/nod...

Comment #4

carlhinton commented 27 September 2011 at 11:04

I am having similar problems with a number of my sites. node?page=xxx node/XXX /user/[uid]/profile/profile and /users/[username] all seem to be vulnerable. This should have a priority much higher than normal - this is users profile information we are talking about!