Exposes "Content pane" Views displays as fields in Display Suite.

This can be used to display associated or related entities for nodes, taxonomy terms, etc.

This functionality is already available with Display Suite "dynamic fields", but Views Content DS is way more convenient for this particular use case.

This module is back! (Feb 10, 2014)

In June 2013 I decided to set this module to sleep, since there is an alternative:
Display Suite "dynamic fields".
#1701824: Views content and DS?

Now (Feb 2014) I changed my mind, and the module is back with a fresh 7.x-2.x branch.

The main difference to the 7.x-1.x branch is that now one separate views_content_ds field is available for every views_content views display for the entity type. Field settings are preserved thanks to hook_update_N().

Which version?

The 7.x-1.* branch exposes one display suite field per view, even if that view has multiple content_pane displays. Each content_pane display of this view is exposed as a formatter. This means you cannot have two displays of the same view on one entity view mode.

The 7.x-2.* branch exposes one display suite field per views display. This allows to easily have more of them in one entity view mode, but the field UI gets easily crowded if you have many content_pane displays.

I changed my mind about this quite a few times, and you are welcome to leave feedback.
I think it depends which site you are working on.
Maybe the solution is to always start with the less crowded option, and then make it possible to activate additional instances per view mode.

How to use, part I: Modules to be installed

drush en views_content_ds

How to use, part II: Create the views display

Note: If you are using e.g. Organic Groups, then the views display might already exist!

Install views_content (shipped with ctools), and create a view and a views display using the "Views content pane" display type.

Configure the "argument mode" of the views display as e.g. "node > content id", or something else depending which entity type you want this to work with.

You probably want to use the argument in the "contextual filters" section of the views display, to filter the content shown in the view, but you don't absolutely need to.

So far, this is all identical with what you would do with plain views_content + ds dynamic fields.

How to use, part III: Configure the entity view mode

Install Display Suite, if you have not already.

Install views_content_ds.

Now go to "manage display" for the node type or entity type/bundle where you want the view to show up, and choose the view mode you want to work on. Choose a display suite layout for this view mode, so that you see all the DS-specific fields. (The simplest are "one column" and "reset").

The views display should now show up as a field, named "(view name): (display name) (Views content DS)", next to the other fields e.g. title, body etc. Move this into the visible section.

If it does not show up, try clearing the caches.

Alternatives

As mentioned, there are alternatives.
- Display Suite "dynamic fields".
- EVA
- Taxonomy display (for taxonomy pages)

EVA

Another alternative to views_content_ds is EVA. EVA has its own display type. You create an EVA display, which is then available in field UI.

Differences:

  • Views content DS only works with display suite enabled displays. EVA views are available in field UI, independent of DS.
  • Views content DS is designed to have a performance benefit over EVA in its current version. See #1617030: Make EVA not be a preprocess field.
  • Views content DS works with views content pane displays, as provided natively e.g. by Organic groups. So, you don't have to create a new views display, but can simply use or clone the existing one.

Taxonomy display

Taxonomy display can be used to display content associated with a taxonomy term, on the taxonomy term page, using either the core listing or Views.

Differences:
Taxonomy display will always display the list of associated stuff below the rest of the entity. E.g. for a taxonomy term with a description, the description will be at the top.

Views content DS allows to place the list of content somewhere in the entity layout, e.g. above the description, or in a column next to it. It also allows to display multiple views displays, at multiple positions in the layout.

Project Information

Downloads