Can I include nodes in a view's results only at URLs specified in the nodes?

Question

Is it possible to conditionally include nodes in a view based on the paths specified in a field on that node? The idea is to essentially mimic the default property of blocks, making their display allowed or disallowed at specified paths. My view (technically a view block) is being used to show sponsor images as a slideshow, and I'd like to be able to define which pages each specific sponsors' graphics should display.

I'd imagine it would include the use of a contextual filter on the field containing the paths, but I can't figure out how it would work. Possibly via some implementation of Views Argument Substitutions, although that seems to base its results off of specified path arguments and not the whole path. In the meantime, I'm implementing Nodeblock as a partial substitute, but I'd prefer to leverage views if possible.

EDIT: Thanks to mchar's answer below, I was able to get a working snippet for this functionality. It could probably be optimized, but that's for another thread.

function MYMODULE_views_pre_render(&$view) {
    if($view->name=='sponsors') {
        $current_path = drupal_lookup_path('alias',current_path());
        foreach($view->result as $row_num => $row) {
            foreach($row->field_field_urls_to_show_up_on as $urlNum => $url) {
                $this_path = $url['rendered']['#markup'];

                // If the path contains an asterisk
                // Asterisks should only appear at the end of a path at the time of writing
                if (strpos($haystack = $this_path, $needle = '*') !== false) {
                    $this_path = str_replace('/*', '', $this_path);
                    if (strpos($haystack = $current_path, $needle = $this_path) === false) {
                        unset($view->result[$row_num]);
                    }
                }

                // if current_path is not the same as the provided path (no *)
                elseif ($current_path != $this_path) {
                    unset($view->result[$row_num]);
                }
            }
        }
    }
}

Answer 1

Hook views_pre_render should meet your needs.

Here is a sample code of what you are describing:

$string_pos = strpos($haystack = current_path(), $needle = 'chickens'); // or you may use drupal_get_path_alias()
  if ($view->name == 'view_name' && $view->current_display == 'view_display') {
    foreach($view->result as $row_num => $row) {
      if ($string_pos && strpos($haystack = $row->node_path, $needle = 'chickens')) {
        unset($view->result[$row_num]);
      }
    }
  }

It can be optimized but I guess you got the idea.

Hope that helps!

Answer 2

1. Add an Entity reference field in the sponsor image content type.
2. On every sponsor image node, refer the master content to which you need this sponsor to be displayed with.
3. In your view, add a contextual filter on the above entity reference field, and Provide the default value -> Content ID from url.

This will filter the sponsor images those only refer the current node in the entity reference field.

Answer 3

A> For non-node pages, set up a taxonomy with terms like the below and add it as a field to your sponsored posts content type.

User Pages
Search Pages
Login Page
Homepage
About Page
etc.

Then create multiple view blocks with each one only displaying on those pages using block settings. In each view, filter by that taxonomy term.

B> For node pages without panels, use Kevin Siji's answer.

C> For node pages that use panels, use Kevin Siji's answer but create a content pane. In Pane Settings, click Argument Input and select "From Context>Content ID" or maybe "From Panel Argument" but I think it's the first one.

That way, your sponsor can choose either nodes, page types, or both.

Bonus> For choosing nodes when creating a sponsored post, you can go one step further and have your entity reference field use an "entity reference view" to decide which nodes can be selected.

This allows you to add things like tiers where the user can choose "premium posts" for example. It also allows you to decide if sponsored posts should show on a regular node when you're creating it. Taxonomy or Booleans can achieve this because your "entity reference view" can filter them.