Drupal 7 Contextual Filter on URL Alias

Question

I have a view which shows a list of articles, located at:

mypage.com/articles

Each article is linked to its main sub page view, like this:

mypage.com/articles/name-of-my-artile-yay

The URL path is created with autopath & URL aliases.

In views, how do I create a contextual filter to show only the selected sub page view?

I have this as my path in views:

articles/%

but don't know where to go from here. I tried title and making it lowercase and replacing spaces with a hyphen, but that won't always work and the URL aliases change the URL such that it removes words like:

a, an, as, at, before, but, by

And if a page title is:

This is my page title - with this

The URL alias becomes:

my-page-title

Therefore it won't be able to match in my contextual filter using the page title.

What am I missing?

Answer 1

I think the simpliest way is to use Panels, and override the Node page. Add a variant and put your view in it, and send the node's nid argument to it, using node:nid contextual argument.

1. (install page manager)
2. Enable node view page (node/%node)
3. Add a variant, set a validation criteria selecting your concerned node type
4. Use simple one-column display
5. Add your view in your column
6. It asks for an argument, send the node:nid, (or entity_id, or whatever)
7. In your view, use node:nid contextual filter

All is done.

Answer 2

Set path alias for the content type to something like articles/[node:title]

Option 1: using views to run detail pages

In views:

1. Create a Page view with the path set to the /articles/%

2. Add Contextual filters Content: Nid and set it to the following:

   • When the filter value is NOT in the URL => Provide default value
   • Type => Raw value from URL
   • Path => Component 1 (Check "use path alias")

This does a path lookup on the last url segment (something like "my-article-title-path-alias") and returns the correct node ID.

Option 2: By-pass views to run detail pages

Instead of setting the path as /articles/% simply set it as /articles and let the all the path aliased /articles/% nodes resolve normally.

Answer 3

Add a contextual filter for the node ID and provide the default using PHP:

if (isset($this->view['args'][0])) {
  $path = db_query("SELECT source FROM {url_alias} WHERE alias = :alias LIMIT 1", array(':alias' => 'article/' . $this->view['args'][0]))->fetchColumn();
  if ($path) {
    $parts = explode("/", $path);
    if (isset($parts[1]) && is_numeric($parts[1])) {
      return $parts[1];
    }
  }
}

return FALSE;

This will return, for example, node/123 if node 123's title was My the Page and Title and you accessed the View at example.com/the_view/my-page-title.

Answer 4

**Contextual filters**

1) Global: Null 2) (article) content/node: nid When the filter value is NOT available Provide default value : Raw value from url

Answer 5

Try this approach...

you first grab the normal drupal path "node/nid" then, you take the nid to load the full load and then use the node title as contextual filter.

1) Get the normal path of the current node being viewed...

<?php
$ogpath = drupal_lookup_path("source",$_GET['q']);

2) This may be expensive but try it ... get the current nid

$ogarray = explode('/', $ogpath);
$node = node_load($ogarry[1]);
return $node->title;

Tell me if it works.

Your pathauto is stripping words in a way I haven't come across yet, are you sure it is configured correctly?

Answer 6

I had a very similar problem and I not just found the solution to it, but also learned new things about how view works. Let me share what I learned and the solution to your problem too.

When you are creating a view with one or more contextual filters, the view must receive values of those filters from somewhere. This can be done by -

1. Picking the context filter value(s) from the URL
   • Typically you would have a page view for such purposes one that has URL of the form foo/%/bar or foo/bar/% for single contextual filter OR of the form foo/%/bar/% or foo/bar/%/% for multiple filters
   • In case you have multiple filters, the url value that appears first is mapped to the first filter, next to the second filter and so on.
2. Views allows you to tell what to do if the filter values are not available in the URL. This is typically used for block views.
   • You can choose from different actions and then configure the choice too. asdfj kajsdf
3. Another thing views allows you is to tell what to do with the filter values if they are found in the URL as described in #1 above. Typical use cases are - Making dynamic titles based on filter values, Validating filter values etc.
   • When validating filter values, you can change the values too! (That is where our solution lies btw). This is very akin to the way we can change $form values in the drupal form validation callbacks.

Solution to your specific problem lies in using a very similar code in the sections pointed to by the arrows in the above image.

Here is the link that proved out to be great help to me - http://www.drupalfoo.com/drupal-7-views-contextual-filter-argument-node-reference-using-url-alias