I am new to views and this might be a noob error but:

I am getting the behavior that when I swap the order of two fields (in the Fields) section, it changes what is displayed. Currently I have a very complex schema, with 8 content types all with node-reference fields pointing to eachother. The two fields in question belong to the same content type, but the content type is referenced by two different types of parent nodes.

Simple Schema:
A --> B
|
C --> D --> B

(it is important to note that the actual node referenced by A is a different instance of B, than the one reference by D)

The fields in question belong to the content type B. But I have two relationships set up that make reference to B (A-->B and D-->B). When the A-->B relationship field comes first in the field order it outputs the A-->B data on both fields. When I rearrange the order of the fields so that the D-->B relationship field comes first, both fields in question get the D-->B value. I'm not sure if this is two bugs or one but it seems that:

1) the value of a field should not depend on the order in which it shows up in the Fields box
2) assuming that a different relationship is used for the two duplicate fields in question, you should get different values

Due to my complex schema nature I'm not including an export of content types and views because it would be 5 miles long. I will if this problem can't be recreated easily.

Comments

merlinofchaos’s picture

merlinofchaos commented

Does this patch fix this problem? http://drupal.org/node/317271#comment-1459264

russbollesjr’s picture

russbollesjr commented

It fixes the problem i spoke of. But the view I'm using has a field which is a node link. Before the patch, the view returned the link but no longer.

For example:

A --> B
|
C --> D --> B
|
E
|
F

So the view is supposed to return a node link to F (and it did before the patch). Any ideas why your patch would change this?

russbollesjr’s picture

russbollesjr commented

i used a workaround. instead of a node reference. I added a node title field and had it link to the node. that works just fine.

merlinofchaos’s picture

merlinofchaos commented
Status: Active » Fixed

As per #2, the problem reported is fixed, and that patch is checked in. If there is another problem, which #2 indicates there may be, please file a separate issue. (And I can't answer the question, I don't quite understand it. There's not enough information).

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.