Add a 'related nodes' block that links to a taxonomy-based view

It works greatly, except I need to show all the related posts EXCEPT the current node?

Here is the solution:

1. Add two arguments, the first one is NODE:Node_id with 'not equal' option and the second one is TAXONOMY:taxonomy_term_id (with no special options).

2. Add the following argument handling code:

3. Add filter node: distinct.
4. Add a sort criteria to sort it by decending node update time.
5. Of course, display the field node:title.

Amnon
-
Drupal Focused Search Engine | Drupal Israel | Organic Web Strategy Consulting

I have struggled myself with the argument handling code for a little while. I guess this is because there is some part "missing" in the manual of the views argument handling code that was definitively not intentional by the great "views" guys (the views module absolutely rocks and gives Drupal an enormous boost setting it apart from any other CMS I know by lightyears of technology!). Most likely they as well as many advanced views people just were a little too deep into their own material as to step back a bit and return to the level of a novice! ;-)

Let me help explain to those who have problems making the views argument handling code work!

First of you need a view. And you want to use the argument handling code because this provides some filtering not available by the included arguments. THIS is exactly the point where many, like me, make the most important error: I have seen it as either-or, and not as in-combination-of with regards to the argument handling code, which, if you do think a little further, certainly is stupid, but never mind, I was on the wrong track for about a day or so myself.

So, to make a long story short: whenever you use the argument handling code, you must also use a "normal" argument from the list of build in arguments! I first thought that if you entered anything in the argument handling code box, this would already work!

So if your argument handling code generates an array node IDs, you must certainly also pull down Node: Node ID from the list of built in Arguments!

So the Argument Handling Code does not work on its own, it provides an existing Argument "filter" with additional information.

Anyway: this might have been absolutely obvious to most of you, I just thought it would be helpful to include in the handbook just for making the point clear to everyone ;-)

Steve

Here's what I did to make this work.

1 - I have created a basic view. It has only a block defined. (This code would work oddly on a page, if at all.) The view type is list view, with 10 nodes per block.
2 - The fields included are only the Node: Title.
3 - Then, for Arguments, I have Taxonomy: Term ID with Display All Values as the parameter.
4 - Paste the snippet above into Argument Handling Code. Make sure the $vid value is the right one for the vocabulary you want to use. (To find the VID of a vocabulary, go to edit that vocabulary and look for the number at the end of the URL on the edit page.)

You could add more filters if you wanted to further limit the results, e.g. only to specific node types, and/or a sort order.

Note that you will want to show this block only on pages which have taxonomy items defined; an error will be generated otherwise. I'm not sure yet what code you need to put in the Page Specific Visibility Settings section of the block configuration. I'll post here if I figure it out.

Edit: You can also use

To get related content displayed in a block view, whether watching a node or a taxonomy, you could do something like this:

Arguments should be node id and taxonomy term id, in that order. And yes, arguments and argument code is a mess, perhaps if things were named differently it would be easier to grasp

I simplified the argument code for performance.

Views Argument Code

taxonomy_node_get_terms() is more database 'expensive' than a tailored single query.

Argument: Taxonomy: Term ID - Display All Values
Argument Code:

Block Visibility PHP Code:

Note: don't load the entire node object as that is an expensive DB operation to add to every page load, checking the node path will suffice:

P.S About arg()

arg() is a function that returns parts of the non-url-aliased Drupal path (the true path)
e.g: node/123/edit
arg(0) = 'node'
arg(1) = '123'
arg(2) = 'edit'
more information is here:
http://api.drupal.org/api/function/arg/5

About Views Arguments

Views arguments ($args) are different from arg().
$args = the array of returned values from the argument handling code
arg() is a function to get parts of the non-aliased url path
AFAIK:
In terms of Views arguments, the argument handling code should return an array.
The array keys (0,1,2 etc...) correspond to each view argument, in order
The array key's value corresponds to the value to pass to that argument for the view
e.g:
$arg[0] = '{term ids}'
$arg[1] = '{second view argument parameters}'
etc...

Exported Related Headlines View

Hope that helps :-)

Been upgrading my site and I used to use a php snippet for this functionality but I found this new module that does this:

http://drupal.org/project/similarterms

marcopolo ---
Blog Marco | Share Trading |

How to add for every term a new block, each of them displaying "related nodes" to respective terms associated with the displayed node:

1. Make a view as described above, but with argument handling code:

2. Set the title to:
articles about %1
"%1" will be substituted by your term

3. Repeat steps 1 and 2, but in the argument handling code, replace
$tids = $tids[0];
with
$tids = $tids[1];
This will add a block with nodes related to the second term of the displayed node.