Closed (fixed)
Project:
Hierarchical Select Node Reference
Version:
6.x-1.x-dev
Component:
Documentation
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
20 Nov 2009 at 15:47 UTC
Updated:
8 Apr 2011 at 16:05 UTC
Comments
Comment #1
jrao commentedI wrote some simple documentation and screenshots at http://drupal.org/node/626088, let me know how I can improve them.
Comment #2
drupov commentedHi and thanks for your quick reply!
My question arises from following matter:
I have created a content type "Continent" and a content type "Country".
"Country" has CCK field named "Continent", which is of type "Node reference" and Widget type "hierarchical select". Under Global settings "Country" has "Required" enabled, Number of values set to "1" and under Content types that can be referenced "Continent" is checked. These settings are saved.
When I go and edit this CCK field after saving it the "Node reference path:" stays empty. Shouldn't it contain, as only one content type is the "parent" of "Country" something like "Country.Continent"?
Or am I thinking in a totally wrong direction? What are once again the correct steps if not? A short example of doing it from the scratch would be great. You've already made a documentation about it but there is something I'm missing...
Thanks again!
Edit: I wrote some bullshit above. "Node reference path:" in the above case is empty because that is a hierarchy of 1 (only Continent -> Country). For such hierarchy you normally don't need a HS type widget, do you? :) It is working perfectly though, when the hierarchy gets more deep (e.g. implement a CT City, referenced by Country and so on). Sorry for this confusion!
Comment #3
jrao commentedYes, in order for the path to show up Continent must reference some other content type, otherwise there's no hierarchy. I have updated README.txt to make this clear.
Comment #4
jrao commentedComment #5
daigo75 commentedThanks for the answer, I have the same issue (no node path showing, only one level of hierarchy).
Unfortunately, this means I can't use the Hierarchical Select, as, in one case, I need to select elements only from the very lowest level of the hierarchy. In my case, I'd need to use it to choose the Countries for a Region, and I'd need to list only Countries, without any parent.
It's true that, in this case, a hierarchical select is not needed, but, since it doesn't handle this case, I'll have to drop it altogether as the user interface would become inconsistent.