Can't use node reference fields with multiple values

Posted by Canadaka on September 15, 2011 at 12:53am

6 followers

Issue Summary

If you use a token that contains a node_reference field that has unlimited or multiple values allowed, the token doesn't work. Anyway for this to happen? Maybe take the first in the list?

Comments

#1

Posted by MGN on September 18, 2011 at 4:48am

Category:

bug report

» support request

this sounds like it may be an issue for the token issue queue. But perhaps I need more information to understand the issue. Custom breadcrumbs just makes use of whatever information is provided by the token, it doesn't modify or otherwise process the values returned by tokens. If i understand the suggestion, you might need to create your own token to "take the first in the list" and then use it in custom breadcrumbs.

#2

Posted by skizzo on January 4, 2012 at 12:54pm

@Canadaka: I have a reference field (field_section) with 3 hierarchical taxonomy terms. When editing a breadcrumb and expanding the tokens list I see two expandable entries, reading:

Section	[node:field_section]	Term reference field.
Section	[node:field-section]	Field "field_section".

clicking either one, the second one will expand giving access to such tokens as "The unique ID of the taxonomy term", "The parent term of the taxonomy term, if one exists." etc... Please note that for unknown reasons I recently stopped seeing the second item (the first was still there but would provide only the basic unstructured token), the second token came back when I tried to update the "entity" and "token" module to latest -dev version.

Project:	Custom breadcrumbs
Version:	7.x-2.x-dev
Component:	Code
Category:	support request
Priority:	normal
Assigned:	Unassigned
Status:	active

Can't use node reference fields with multiple values

Jump to:

Issue Summary

Comments

#1

#2

#3

#4

#5