"Node: Nodereferrer" fields don't work with relationships
| Project: | NodeReferrer |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
This isn't quite the same issue as #375088: Patch to add nodereferrer relationship to Views, although that helped me find a different solution to my problem.
CASE:
You have a content type (Car) that references another content type (Garage). Build a view of Cars that has a field displaying all the Cars in its referenced Garage.
MY PROCEDURE:
1. Start with a view filtered by Node Type: Car.
2. Add a relationship for Content: Garage.
3. Add a field for Node: Nodereferrer: by node type, using the Garage relationship.
PROBLEM:
This doesn't work. Nothing shows up in the field. The relationship itself is fine: I have another field for Garage Location using the relationship, which works as expected.

#1
3rd step is wrong - you should use None:Tittle for example with this relation
#2
That wouldn't be the goal for this example. Using "Node:Title" here would give me the Title of the Garage. I want to display other Cars that reference the same Garage.
#3
#4
You need view with Cars or view with Garages?
If you need to view Cars by One Garage - check out http://drupal.org/node/375088#comment-1712098
#5
I need a view of Cars, not a view of garages. The view I need is a collection of information about each car, not each garage. One of the necessary fields happens to be "Other cars at this location", and that's the field I would expect to work through the use case outlined above.
But even if I did end up going with a view of Garages, I don't think this issue is quite fixed. Regardless of this particular example, I think the steps I outlined above are in line with the way we understand Views to work generally, and they don't produce the expected output.
#6
I have a similar problem.
The example lesmana stated is valid and I will try to pick it up.
The overall problem is, that you can't set the "Relationship" property for a Referrers Node.
for further use:
Bike--> Garage <-- Car
So "Bike" and "Car" are both referring the Garage.
If you attempt to get all the Bikes, when your initial node is Garage, you can just use Referrers - and it works fine.
If you attempt to get the Garage, the Car is referring to, and the Car is your initial node you will use the content:reference - and it works fine.
However, combining these two: Having the car your initial node, attempting to get the Garage by reference and then trying to get all the "Referrers" of the "Garage" does NOT work. This is because, the "Relationship" combo box in the "node refererrers" object is missing.
I hope this will help!
#7
I downloaded the latest -dev before I wrote my last comment.
Although it didn't work when I tried it for writing my comment, it now seems like it's working.
Since it's getting too late now, and I'm not sure if I'm overlooking something here, I'll comment about it again tomorrow. Sorry for the confusion
#8
Thanx for deep explanation of this case, so I'm waiting the results of final test!
#9
It's working with the latest -dev.
#10
Suppose this fixed
#11
Automatically closed -- issue fixed for 2 weeks with no activity.