This field in conjunction with the Paragraphs module, makes for a very powerful content management system, allowing addition of just about any kind of content into an entity page.

In Drupal 8, Views are now identified as entities and the core Entity Reference Module is able to reference Views, however not Views displays. This module leverages core entity reference module functionality to add the display ID so that a View can be rendered in a field formatter.

This module does the same as View Reference, for which there is currently no Drupal 8 release or any messages on the project page regarding Drupal 8. Because Views Reference leverages Drupal 8 core functionality, this module is quite different from the other module and there is no upgrade path.

For a more complete comparison with other views-embedding modules please check the documentation!

Explanation and features:

  1. Viewsreference is a entity reference field that you add to an entity via the 'Manage fields' tab of an entity.
  2. With Viewsreference you can enter content unique per item of content (eg node) so that one item might have one view and another item might have a dozen views.
  3. If your site has a lot of views, the viewsreference field provides a brilliant substitute to content placement widgets such as context and drupal block admin.
  4. With viewsreference fields you can delegate permissions easily to an editor to add views to a page in a much more intuitive way than either option in #3.

Views reference field currently allows you to set arguments and a title field. The field now has an extra column called data which can be used in an extension of this field type to apply more settings as discussed. The 2.x branch adds changes to already leverage the data field for the available title/argument fields.

2.x Branch

The 2.x branch enables a data property used to store any settings associated with a view, such as show/hide pager or number of results shown. It uses a Plugin Manager to add settings to the views reference fields and enables site builders to hide provided settings for each field instance. The branch itself comes with some settings and developers can add more through custom plugins.

There is an upgrade path from 1.x to 2.x, but please backup your database before doing the upgrade to prevent possible data loss. Please also report any issues you may encounter during the upgrade.

Future development is focused on the 2.x branch.

Supporting organizations: 

Project information

Releases