I'n not exactly sure if this is related to Noderelationships, Nodereferrer or Views (becouse one of these modules is responsible for this, I suppose). Before a while I post an issue at Noderelationship - http://drupal.org/node/620132 - I repeat this post here because this error is very important for me. Sorry for duplicating..

To simplify, in description below I include only those content types which can matter.

I have 4 content types: Archeologist, Graduate, Excavation and Excavation_place.
They are connected via many relations:

  • "Archeologist" can be dissertation supervisor of "Graduate"
  • "Archeologist" can be excavation manager of "Excavation"
  • "Excavation" takes place at "Excavation place"

So, using manually created Views or automated backreferences Views, I can display related data:

  • On "Archeologist" node page, I can display backreferences views to "Graduates" and "Excavations" to which archeologist is responsible for
  • On "Graduate" node page, I can display "Archeologist" which is graduate dissertation supervisor
  • On "Excavation place" node page, I can display backreferences views with "Excavations" which took place there
  • and so on.

I have created proper views and on my localhost everything works flawlessly.
On production server, when I'm logged in as user 1 - too. But for anonymous, and when I login as any other user, I cannot access any specific "Archeologist" node page (Drupal access denied error).
All other referenced nodes ("Excavation", "Excavations place", "Graduate") are displayed OK, even if they contain automated backreferences views included.

I have also no restrictions on views display, and no any custom node access control module installed.

I can't also find any differences between localhost and production server views/references configuration. Permissions to specific CCK fields are the same.

What am I missing?

Comments

merlinofchaos’s picture

merlinofchaos commented
Status: Active » Closed (won't fix)

Views doesn't provide any access control for anything not a View, so Views probably sin't involved in your problem. At a guess, I would check what node access modules you're using -- modules such as og, taxonomy access control, content access, etc. You might consider trying the rebuild access permissions button in the content settings area, too, sometimes the database can get out of sync if modules aren't properly done. Beyond that, I don't have any good ideas for you.

cyc’s picture

cyc commented
Status: Closed (won't fix) » Active

I have no any access modules installed and never had (yet).
Rebuild node permissions was one of the first things I've done.

And I'm reverting status to active, because backreferences are displayed using custom view, so issue still can be related to Views.

merlinofchaos’s picture

merlinofchaos commented
Status: Active » Closed (won't fix)

Uhh. The view itself, sure. but the nodes? No. view has no control over the access to those nodes.

cyc’s picture

cyc commented
Title: denied access to nodes with backreferences for anybody except user 1 » [solved] denied access to nodes with backreferences for anybody except user 1
Status: Closed (won't fix) » Closed (fixed)

I'm closing this becouse I've found a mistake.
My stupid mistake.

After 2 days of reading dozens of forum posts and issues, and after hundreds of clicks, I've realized that all nodes of that specific content type were.... unpublished;-)

This was set as a default during creating content type, but then I've forgotten that, because I was always browsing content as logged user.

Really sorry for engaging community with this..