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), but I will start here (and repeat this post in Views issues list, becouse this error is very important for me).

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

cyc’s picture

cyc commented

topic at Views issues: http://drupal.org/node/620134
Noderelationships developers: feel free to close this issue if you want. Discussion should be at one place.

markus_petrux’s picture

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

Re: "I cannot access any specific "Archeologist" node page (Drupal access denied error)"

Well, this is not related to Noderelationships or Views. Please, check anonymous users have the right permissions to access content and nodes of these particular types. It could be related to Drupal permissions, but also something related to node access module.

cyc’s picture

cyc commented

I'm not 100% sure it's not related to noderelationships or views. This happens on content type nodes containing backreference views generated by noderelationship module. And views have their own access control.
What strange is, it does not happen on all content type nodes containing such fields references - only on that specific one.

markus_petrux’s picture

markus_petrux commented

Noderelationships does not alter the logic to control if node/xx is accesible or not. So it should be something else.

Something you may want to try is print a backtrace from drupal_access_denied().

cyc’s picture

cyc commented

@markus_petrux,
please guide me how.

cyc’s picture

cyc commented
Title: denied access to nodes with backreferences or anybody except user 1 » [solved] denied access to nodes with backreferences or 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..