Closed (fixed)
Project:
Node Auto Term [NAT]
Version:
6.x-1.1-beta3
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
29 Dec 2008 at 20:53 UTC
Updated:
5 Apr 2010 at 20:56 UTC
Jump to comment: Most recent file
Comments
Comment #1
martysteer commentedI 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.)
Comment #2
chlobe commentedI would further confirm this. Nothing to add to the previous bug report, 1.1 beta 2 version.
Cheers
Comment #3
Zen commented'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 ...
Comment #4
anantagati commentedIt 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?
Comment #5
Zen commentedComment #6
chlobe commentedZen 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
Comment #8
ArgentOfChange commentedHi Chlobe,
I'm looking for precisely the same solution. Did you find an alternative way to do it?
Cheers!
Lee-Yan
Comment #9
chlobe commentedHi 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
Comment #10
nemchenk commentedSame request here -- have references to the taxonomy term on tagged nodes point to the NATed node, rather than the taxonomy term.
Comment #11
Alice Heaton commentednemchenk - 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.
Comment #12
nemchenk commentedGood golly, you are correct! Ticking the box on the "target" type works!
Comment #14
anantagati commentedIf 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:
to this one:
Comment #15
anantagati commentedCommitted.
Comment #17
miljats commentedI 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.