Using tokens from other fields that are excluded from the view is broken. [#1142196]

On feeds styles that accept fields ar rows style (e.g. txt, XML) the field "Node: Path" remain fixed to the one of the first item when it is selected as excluded from display and then used as a custom token in an other field using the option "Rewrite the output of this field".

To be more clear ;-) :

- create a view (e.g. of events) and add to it a feed display
- choose style txt
- choose fields Node: Path and Node: Title
- on "Node: Path" field options select "Exclude from the display"
- in "Node: Title" field options select "Rewrite the output of this field" and type "[path] - [title]"

Now you get the path of the first record on all items :-(
I tried with a page and it seems to happen only with feeds..
If I uncheck "Exclude from the display" I got it in both positions the right path.

Comment	File	Size	Author
#2	1142196-using_tokens_broken-2.patch	580 bytes	travist

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

sylvaticus CreditAttribution: sylvaticus commented 29 April 2011 at 10:40

..same with Node: nid...

Comment #2

travist CreditAttribution: travist commented 27 August 2011 at 22:45

Title:	On feeds styles that accept fields ar rows style, "Node: Path" remain the one of the first record	» Using tokens from other fields that are excluded from the view is broken.
Status:	Active	» Needs review

File	Size
1142196-using_tokens_broken-2.patch	580 bytes

I ran into the same issue. The problem is really using Token's that pull in other fields.

After debugging, I figured out that this module is not calling the theme functions if the field is set to exclude. In order for the tokens to work within views, the theme function for every field must be called. Then you can simply not show the output of that field is set to exclude.

Here is the patch that fixes this issue.

Thanks,

Travis.