Closed (outdated)
Project:
Faceted Search
Version:
6.x-1.x-dev
Component:
Taxonomy Facets
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
17 Jun 2009 at 18:07 UTC
Updated:
24 Aug 2021 at 20:02 UTC
Jump to comment: Most recent
Comments
Comment #1
MGParisi commentedI have initial documentation on how to set the default taxonomy value within a module. The documentation is within the Hierarchical Select issue queue waiting for review. Hierarchical select provides a front end interface to force the user to meet certain depth requirements. I do not know if this is checked on the back end.
Comment #2
ErwanF commentedThank you MGParisi for your answer. But the HS module, though it looks very promising, is still unstable on Drupal 6 at the time of writing. Do I absolutely need this module? Anyway, please could you drive me with a link to your initial documentation?
Comment #3
David Lesieur commentedBecause of the way the user interface is currently built, once a term is selected in a facet you don't have access to other terms in the same facet, requiring you to first unselect the current term before choosing another. This is opposite of what you need for your mandatory facet.
What you could do with the current features we have is build a separate search environment for each term in your mandatory vocabulary, have this environment display a view filtered by that term, and then create a custom block with simple links to each of those environments. Your mandatory vocabulary would be accessed by that block rather than a real facet. This may not make sense if you have a lot of terms, and switching environment through those links will cause the user to lose his current search. You judge if that's good enough for your project.
The ideal solution would require some coding.
Comment #4
ErwanF commentedI see. Thanks a lot David for this answer, I will think about this.
Comment #5
MGParisi commentedNow that they opened up documentation, and that I have Doc Admin priv's, I will try to create a few pages on how to do this. The thing is, its not unique to Hierarchical select, but can predefine any taxonomy. So the documentation will need work.
Comment #6
ErwanF commentedThanks for your efforts, MGParisi.
Comment #7
avpadernoI am closing this feature request, since it has been opened for a project version no longer supported. If you want this feature implemented in a supported project version, please re-open this request.