Great module, thanks.

All installed and works great, except for a small glitch in the site confiuration that doesn't appear to save the change when I check any term's box for:

'Make NAT terms in xxxx node views point to the associated node rather than the taxonomy page.'

All links still refer to the taxonomy pages, rather than the node pages

Thanks again

Stu

Comments

martysteer’s picture

I have this problem too. I thought it might be a path_auto module conflict, or something so I've just finished testing on a clean install without any extra modules installed and the hook_link_alter() still appears not to affect the taxonomy links. I can't see where it's going wrong.

This feature was added to the 5.x version a while ago (http://drupal.org/node/144864).

I'm not sure in which 6.x version it's become broken. I'm considering testing out the Category module to see if it alters taxonomy links correctly (even though it's a bit more complicated than I need.)

chlobe’s picture

I would further confirm this. Nothing to add to the previous bug report, 1.1 beta 2 version.

Cheers

Zen’s picture

'Make NAT terms in xxxx node views point to the associated node rather than the taxonomy page.'

You might be setting this up backwards on your sites - I agree that it's a little unintuitive ...

anantagati’s picture

Category: bug » support
Status: Active » Postponed (maintainer needs more info)

It works for me.

If I check for example for story node (Make NAT terms in story node views point to the associated node rather than the taxonomy page.) and go to story node link to term is pointing to node associated through NAT.

What exactly doesn't work?

Zen’s picture

Status: Postponed (maintainer needs more info) » Fixed
chlobe’s picture

Category: support » feature

Zen picked up exactly what the problem was in the phrasing of 'Make NAT terms in story node views point to the associated node.' I was having the same problem as those previously noted - we were overlooking the fact that views meant VIEWS rather than generically referring to a taxonomy page versus a node page view (presentation).

The problem then still remains for me which is clearly a feature request: I am using a tag cloud to display terms as a feature on a page. Tags rightly link directly to taxonomy pages whereas I need them to point to the node itself itself (as the node and the taxonomy are 1=1 that is one node per taxonomy so it is a little daft to have a taxonomy page of one node).

Cheers

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

ArgentOfChange’s picture

Hi Chlobe,

I'm looking for precisely the same solution. Did you find an alternative way to do it?

Cheers!
Lee-Yan

chlobe’s picture

Hi Lee-Yan

Sorry but no success - it is possible I am led to believe but requires getting under the .js hood which I cannot do.

Sorry I can't be of more help.

Cheers

nemchenk’s picture

Version: 6.x-1.1-beta2 » 6.x-1.1-beta3
Status: Closed (fixed) » Active

Same request here -- have references to the taxonomy term on tagged nodes point to the NATed node, rather than the taxonomy term.

Alice Heaton’s picture

Status: Active » Fixed

nemchenk - this feature already works - it's just not very intuitive (just took me a while to work it out...).

Say you have a content type T1 on which you can use vocabulary V. Using the NAT module you associate content type T2 to vocabulary V.

When you view a node of type T1 (either as a teaser of a page) you want the links to the terms of vocabulary V to point directly to the nodes of type T2.

In order to achieve this, go the NAT settings page (/admin/settings/nat) and enable "Make NAT terms in categories node views point to the associated node rather than the taxonomy page." ON CONTENT TYPE T1. Doing this on content type T2 (which seemed more intuitive to me at first) does not give the expected result.

nemchenk’s picture

Good golly, you are correct! Ticking the box on the "target" type works!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

anantagati’s picture

Title: Doesn't point to associated node » Doesn't point to associated node if Taxonomy term has path alias
Category: feature » bug
Status: Closed (fixed) » Needs review
StatusFileSize
new862 bytes

If Taxonomy Term has path alias and 'Make NAT terms in node-type node views point to the associated node rather than the taxonomy page.' is checked it doesn't change taxonomy link to NAT node.

Problem is in function nat_link_alter(&$links, $node), where Term Id is read from link which is already that time changed to path alias.

Bug can be fixed by changing this line:

  $tids = array(str_replace('taxonomy/term/', '', $link['href'])); 

to this one:

  $tids = array(str_replace('taxonomy_term_', '', $module));
anantagati’s picture

Status: Needs review » Fixed

Committed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

miljats’s picture

I installed (fresh install) 6.x-1.2 and followed the instructions. I set the option "Make NAT terms in categories node views point to the associated node rather than the taxonomy page" cheked in content type where term appears, just like Anselm Heaton described earlier, and nothing hapend. Term doesn't point to associated node. Path alias module is installed.