Closed (works as designed)
Project:
Hierarchical Select
Version:
6.x-3.3
Component:
Code - Content Taxonomy
Priority:
Minor
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
24 Aug 2010 at 07:02 UTC
Updated:
26 Aug 2010 at 08:19 UTC
I'm using HS on my site kirigaha.info and so far it has been working fine (e.g. to hierarchically select car models, etc.)
But now I'm creating a new content type (laptop) where there are 2 HS vocabs - one for model (e.g. HP -> Pavilion) and another for Processor (e.g. AMD Turion 64 X2 -> TL-52).
The model is displaying as expected, but the Processor doesn't display as Hierarchical text, but does display as normal text.
Please see http://kirigaha.info/laptop/1
It should display the processor ("AMD Turion 64 X2 TL-52") between "Mid Size" and "(Dual Core)" but the output seems empty
At the end of the view, I added the same field as hierarchical links (still no display) and text (does display)
However, I don't think this is a views problem, because the same field is set to display below, (in the Basics group) and there too it only displays if set to text (right now it's set to hierarchical text and therefore doesn't appear)
I am using theme overrides to change the separator to a space, but I tried disabling that and it still doesn't work
To see if there is an issue with 2 HS elements on the same page, I changed the order so that the processor is displayed before model, but still processor didn't display and model did. So it would appear to be a problem with the field itself, than the order.
Help me please :(
Comments
Comment #1
sifaan commentedFor now, worked around it by adding two fields in views (display as text), and displaying the top level term separately from the lower level term and using CSS on both fields... not the most elegant way of going about it, and seems a shame when the heirarchical text output type works fine elsewhere
Comment #2
wim leersCan you reproduce this on a vanilla Drupal installation?
Comment #3
sifaan commentedDiscovered the problem... the fields that were being saved as Processor were part of a larger vocabulary (and in CCK, I had specified a parent term). Even with the parent term, selecting terms when creating nodes worked OK, and displaying as text worked ok, but displaying as hierarchical text didn't.
Because setting up a HS filter for views doesn't work with parent term restrictions, I moved the terms to a new vocab and the display as hierarchical text works fine.
Bottom line, don't use parent terms to restrict Content Taxonomy to parts of vocabularies if you plan to use HS - pull it out as a seperate vocab.
PS: Sorry, changed priority by accident
Comment #4
wim leersOk, thanks!