 readme  id readmetxt v 142 20110206 135718 wimleers exp description this module defines the hierarchicalselect form element which is a greatly enhanced way for letting the user select items in a hierarchy hierarchical select has the ability to save the entire lineage of a selection or only the deepest selection you can configure it to force the user to make a selection as deep as possible in the tree or allow the user to select an item anywhere in the tree levels can be labeled you can configure limit the number of items that can be selected configure a title for the dropbox choose a sitewide animation delay and so on you can even create new items and levels through hierarchical select integrates with forum drupal core menu drupal core taxonomy drupal core content taxonomy http drupalorg project contenttaxonomy views installation 1 place this module directory in your modules folder this will usually be sites all modules don t install your module in drupal core s modules folder since that will cause problems and is bad practice in general if sites all modules doesn t exist yet just create it 2 enable the module 3 if you want to use it for one or more of your vocabularies go to admin content taxonomy and click the edit link for a vocabulary now scroll down and you ll find a whole range of hierarchical select settings all settings are explained there as well troubleshooting if you ever have problems make sure to go through these steps 1 go to admin logs status ie the status report ensure that the status of the hierarchical select module is ok 2 ensure that the page isn t being served from your browser s cache use ctrl r in windows linux browsers cmd r in mac os x browsers to enforce the browser to reload everything preventing it from using its cache 3 when you re getting a js alert with the following message received an invalid response from the server ensure that the page of which this form is a part is not being cached 4 when hierarchical select seems to be misbehaving in a certain use case in which terms with multiple parents are being used make sure to enable the save term lineage setting note you may have to repeat this for every configuration in which the vocabulary with terms that have multiple parents are being used eg if such a vocabulary is called a then go to admin settings hierarchicalselect configs and edit all configuration that have a in the hierarchy column in case of problems don t forget to try a hard refresh in your browser limitations creating new items in the hierarchy in a multiple parents hierarchy more scientifically a directed acyclic graph is not supported not the entire scalability problem can be solved by installing this set of modules read the maximum scalability section for details the child indicators only work in firefox this cannot be supported in safari or ie see http drupalorg node 180691 comment1044691 the special savelineagetermpath token only works with contenttaxonomy fields as long as you have the save option set to either tag or both in hierarchies where items can have multiple parent items and where you have enabled hierarchical select s save lineage setting it is impossible to remember individual hierarchies unless the underlying module supports it so far no module supports this hierarchical select is just a form element not a system for storing hierarchies for example if you have created a multiple parent vocabulary through the taxonomy module and you have terms like this a c a d b c b d if you then save any two lineages in which all four terms exist all four lineages will be rendered by hierarchical select because only the four terms are stored and thus there is no way to recover the originally selected two lineages you can not expect the hierarchical select taxonomy module to automagically fix all existing nodes when you enable or disable the save lineage setting and neither can you expect it to keep working properly when you reorganize the term hierarchy there s nothing i can do about this hierarchical select is merely a form element it can t be held responsible for features that drupal core lacks or supports poorly see the following issues http drupalorg node 1023762 comment4054386 http drupalorg node 976394 comment4054456 maximum scalability hstaxonomy takes advantage of the taxonomyoverrideselector variable to improve scalability the whole tree is no longer loaded by drupal core while the hsbook hsmenu and hssubscriptions modules override existing form items those form items are still being generated this can cause scalability issues if you want to fix this you will have to modify the original modules so that includes drupal core modules simply move the changes from the hookformalter implementations into the corresponding form definitions hierarchical select taxonomy using the savelineagetermpath token when you re using the token module and likely the pathauto module and you ve configured your hierarchical select to save the lineage you may want to show the saved lineage or the first lineage in case you ve also enabled the dropbox in your url that s possible through the savelineagetermpath token and other similar tokens however by default it uses the separator you ve configured pathauto to use if you aren t using pathauto then it will default to a dash you can override this by setting the hstaxonomyseparator variable also when you re using pathauto and it seems to be stripping the separator you ve configured then you may want to configure that character in pathauto s punctuation settings to no action do not replace using the dropbox in views exposed filters this can be very tricky due to a combination of the respective limitations of taxonomy and views exposed filters see http drupalorg node 346033 rendering hierarchy lineages when viewing content hierarchical select is obviously only used for input hence it is only used on the create edit forms of content combine that with the fact that hierarchical select is the only module capable of restoring the lineage of saved items eg taxonomy terms none of the drupal core modules is capable of storing the lineage but hierarchical select can reconstruct it relatively efficiently however this lineage is only visible when creating editing content not when viewing it to allow you to display the lineages of stored items i have provided a theming function that you can call from within eg your nodetplphp file the themehierarchicalselectselectionaslineages selection config function sample usage using taxonomy and hierarchical select taxonomy this will automatically render all lineages for vocabulary 2 meaning that if you want to render the lineages of multiple vocabularies you ll have to clone this piece of code once for every vocabulary it will also automatically get the current hierarchical select configuration for that vocabulary alternatively you could provide the config array yourself only three keys are required 1 module 2 params 3 savelineage for example if you don t like how the lineage is displayed simply override the themehierarchicalselectselectionaslineages function from within your theme create eg garlandhierarchicalselectselectionaslineages setting a fixed size when you don t want users to be able to resize a hierarchical select themselves you can set a fixed size in advance yourself setting size to 1 does not generate multiple true selects and the opposite is also true multiple sets the multiple html attribute this enables the user to select multiple options of a select size just controls the size html attribute this increases the vertical size of selects thereby showing more options see http wwww3org tr html401 interact formshtml adefsizeselect sponsors initial development paul ektov of http autobinru abstraction to let other modules than taxonomy hook in etienne leers of http creditcalcbiz support for saving the term lineage paul ektov of http autobinru multiple select support marmaladesoul http marmaladesoulcom taxonomy subscriptions support mr bidster inc ability to create new items levels the worx company http wwwworxcocom ability to only show items that are associated with at least one entity merge http mergenl views 2 support merge http mergenl author wim leers website http wimleerscom contact http wimleerscom contact the author can be contacted for paid development on this module this can vary from new features to hierarchical select itself to new implementations ie support for new kinds of hierarchies  