Views is an indispensable and powerful module at the heart of Drupal that you can use to quickly generate structured tables or lists of consistently formatted content, and filter and group that content by simple or complex logic. But in pushing Views to do ever more complex and useful things, we can sort of paint ourselves into a corner sometimes. For instance, I have many times created multiple Views displays on a single page that contain overlapping content. My homepage has a Views display of manually curated content, using Nodequeue or a similar module. On the same homepage, I have a Views display of news content that shows the most recent content. Since the two different Views displays pull from the same bucket of content, it is very possible to have duplicate content across the displays. Here is an example:
Notice the underlined duplicate titles across the two Views displays.
This is what we want:
Notice the missing featured titles from the deduped Views display.
By creating a custom Drupal module and utilizing a Views hook, we can remove the duplicate content across the two Views displays. We programmatically check exactly which pieces of content are in one View, and we feed that information to a filter in the second View that excludes it.
- You are using Drupal 7
- You are familiar with Views module
- You know how to install modules
- You know at least a touch of PHP
My example code assumes that you have created two Views displays.
- Featured - A View display of manually curated content. This display will be used to generate a list of content to exclude from our automated Views display.
- Automated - A View display of news content that shows the most recent content. This display will accept a list of content to be excluded.
You can of course adapt the Views displays to your exact needs.
After creating the Views you wish to use, you’ll need to know the machine name of the View and View display.
One way to retrieve these names is from the view edit URL. While editing your view, notice the URL:
/admin/structure/views/view/automated_news/edit/block
In my case, automated_news is the view name and block is the view display name.
Make a note of your machine names for Step 3
On the view you wish to dedup or exclude content from, you’ll need to add and configure a contextual filter.
- Navigate to edit the automated content view
- Under “Advanced” & “Contextual Filters”, click add and select “Content: Nid (The node ID.)”
- Select “Provide default value” and choose “Fixed value”.
- Leave the Fixed value empty as we’ll provide this in code
- Under “More” select “Allow multiple values” and “Exclude”
- Save the view
Enable your custom module that contains the deduping code. You are welcome to download the example module on Github and use it, or add the code to an existing custom module if it makes more sense. In any case, you’ll need to customize the module a little bit to work with your Views.
- Update the machine name variables from Step 1. See $featured_view_name, $featured_view_display, $automated_view_name and 2. $automated_view_display
- Save your module
- Enable your module
- Clear your Drupal cache
If everything was configured correctly, you should see your Views displays properly deduped.
View Example Code on Github
The code relies on hook_views_pre_view(), a Views hook. Using this hook, we can pass values to the Views display contextual filter set in Step 2. Here is a version where content IDs (NIDs) 1, 2, 5 & 6 are manually being passed to a view for exclusion.
<br /> /**<br /> * @implements hook_views_pre_view().<br /> *<br /> * https://api.drupal.org/api/views/views.api.php/function/hook_views_pre_view/7<br /> */<br /> function hook_views_pre_view(&$view, &$display_id, &$args){<br /> // Check for the specific View name and display<br /> if ($view->name == ‘automated_news’ && $display_id == ‘block’) {<br /> $args[] = 1+2+5+6;<br /> }<br /> }<br />
There are many ways you could dynamically build a list of NIDs you wish to exclude. In my example, we are loading another Views display to build a list of NIDs. The function views_get_view() loads a Views display in code and provides access to the result set.
<br /> // Load the view<br /> // https://api.drupal.org/api/views/views.module/function/views_get_view/7<br /> $view = views_get_view('automated_news');<br /> $view->set_display('block');<br /> $view->pre_execute();<br /> $view->execute();</p> <p>// Get the results<br /> $results = $view->result;<br />
Drupal Views is a powerful module and I like the ability to extend it even further using the extensive Views hooks API. In the case of my example, we can keep using Views with writing complex database queries.