Hi,
I have a cck content_type (mytype) with a content_taxonomy field (state, wich comes from category state). I want a view that shows the nodes "mytype", passing the "state" as argument to view the nodes "mytype" from particular "state". The URLs are like:
http://www.example.com/viewwitharg/13
taxonomy 13 is, for example, state "New York". Everything works fine, ok.
Now I want the title for that view page, like: "Products from New York", so as I understand I must define in the view, arguments section, "Taxonomy Field: State" row, the field Title as: "Products from %1".
So here comes the problem... I don't see "Products from New York" as a title, I see the correct items in the page (the view works fine), is just the title... I see "Products from" only, it looks like there is some problem with the "Taxonomy Field" so it doesn't provide the name of the taxonomy or something.
It's a content_taxonomy issue? it's a views issue? Am I doing something wrong???
Please, I need help with this!!!
Thx!
Lluis
Comments
Comment #1
llribas commentedI forgot commenting I have the content_taxonomy field, in the definition of the content_type, "Save as: CCK only", must I try with "Save as: both"???
Comment #2
ray007 commentedThis did work in an early version of the module, but current versions don't work anymore.
To use the taxonomy in views you must save the data "as tag" or "both", otherwise it doesn't get written to the node_term table.
You need to use "both" if you also want the value displayed in the node without extra theming magic.
The problem is that the wrong value is written to the tid-field in the node_term table and therefore the view doesn't find anything ...
Comment #3
ray007 commentedI think that in
content_taxonomy_field()undercase 'insert':you need to change the 2 lines sayingto
But something else seems to modify $node->taxonomy afterwards and so I get junk in my term_node table ... no idea yet what's going wrong.
Hmm, am I in the right issue here, or should I have opened another one?
Comment #4
mh86 commentedthe views support for content taxonomy has been much improved some time ago. I think this solves your problems..
Comment #5
(not verified) commented