Views Reference Field

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

Key features

• Allow editors to decide where and when to display Views in their site
• Allow editors to add as many different Views as they would like to a page when a site builder adds this field to a Paragraph or Layout Builder block for example
• Allow editors to decide which Display within a View to show (without this module, Core's entity reference would allow the View selection only)
• Allow editors to customise how each View is display with the use of the built in Settings plugins
• Allow developers to build out their own range of controls to give the editor, even leading to a sort of listing builder so editors can control content lists without needing to understand Views or be an experience Drupal site builder
• Automated test coverage to ensure you have a reliable tool for your sites

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

How to use this module

1. Add a Views Reference Field to any fieldable entity (like Node, Paragraph, Block, User, etc) via the 'Manage fields' tab of that entity
2. Decide which Views to allow (or all) via the field settings
3. Decide whether to give the editor control over these built-in settings
   1. View arguments (contextual filter)
   2. Showing the View title or not
   3. Setting the limit and/or offset
   4. Deciding how the pagination is displayed
   5. (Roll your own control, like filters to show, table columns to display, etc)
4. Use 'Manage form display' to decide whether to use an autocomplete or a select list for the editor to choose the View
5. Use 'Manage display' to decide whether to 'Lazy load' the View or render immediately

Views Ajax History and Drupal Core Ajax integration

This module uses a viewsreference query string variable to persist its settings. When used with Views Ajax History or Drupal Core's Ajax (since version 11.3), that query string appears in the URL. Use Views Ajax History version 8.x-1.9 or include a patch of the merged commit to exclude the viewsreference[compressed] from the URL (regardless of your Drupal Core version).

Add-on modules

1. Views Reference Extras extends this module to handle complex configurations which can result in 414 errors but reloading the views reference configuration from the entity instead of compressing the configuration as is.
2. Views Reference Field Filter extends this module by adding a filter plugin that grants control over exposed views filters.