Here is the setup:
- A content type with a field "term reference" for the tags for instance.
- The tags have a description.
- There is a "node_view" panels override for this content type.
- The panel has a context "taxonomy term from node (on node: Tags [field_tags])
- On the panel content I added a "taxonomy term: description"

Now with this I would expect to be able to choose a "standard" view mode, but instead I have "Page of a taxonomy term" and "Tokens". This is wrong I think, the correct view modes would be "filtered html", "full html", "plain text", ...

I previously submitted a patch here #1340950: Filter not used for description in "term being viewed : description"
But it was not fixing the exact issued described there so it has not been committed.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

idflood’s picture

Here is the patch.

before:
before patch

after:
after patch

Status: Needs review » Needs work

The last submitted patch, 1: term_reference_description_filter-1776574-1.patch, failed testing.

mrjmd’s picture

Issue summary: View changes
Status: Needs work » Needs review
FileSize
1.88 KB

Here's a re-roll.

DamienMcKenna’s picture

Why is this any different to any other text field? The way generic fields are handle is that it pushes the control of the renderer back to the normal entity display and lets you choose which view mode to use, so then you have to configure the field at the view-mode level. I would question whether this is by design?

Thoughts, japerry?

Chris Matthews’s picture

The 5 year old patch in #4 applied cleanly to the latest ctools 7.x-1.x-dev, and if still applicable needs to be reviewed and tested by the community.

Checking patch plugins/content_types/entity_context/entity_field_extra.inc...
Hunk #1 succeeded at 76 (offset 4 lines).
Hunk #2 succeeded at 126 (offset 4 lines).
Applied patch plugins/content_types/entity_context/entity_field_extra.inc cleanly.