Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.First-- terrific module. And my experience of it is perhaps an hour (though I have scanned the pending issues) so if this has already been addressed please accept my apologies.
If you have a hierarchical facet (say, 'audience' with 'student' as a subtype with 'current student' and 'prospective student' as sub-types both of 'student'). And you put all the faceted searching in, say, the right block. Then click on term 'student' it will produce the results and the refined 'faceted searching text' but the refined 'faceted searching text' will no longer be in the right block. It will be in the the main content under the results. If you then click on, say, 'current student' you get the results and the refined 'facet searching text' breadcrumb etc. all return to the right block.
If you look at the html code generated in these two cases. The one for the intermediate type (with children) generates a whole lot of unmatched DIVs. It is ill-formed. Whereas the one for the terminal leaf is perfect (and renders as it should).
Not all facets are going to be flat-facets. In fact, hierarchical facets are probably more common.
All the best with this.
Thanks,
Martin
Comments
Comment #1
mfricke commentedI have spent a few hours on this now. And maybe what I have found will shorten the work anyone else does.
1. This is not directly to do with Faceted Search. It is more general than that. You can reproduce it using hierarchical categories, without Faceted Search at all. [But Faceted Search goes wrong here because it relies on that underlying un-soundness.]
2. It seems to be connected with the theme. In particular Garland's page.tpl.php (and similar) render pages like /taxonomy/term/148 incorrectly (where 148 is hierarchical). Some other themes, at least, do not seem to do this.
I do not know why just yet.
Best,
Martin
Comment #2
mfricke commentedok, I think I have resolved this. And there (maybe) is nothing wrong with any of the modules. But I don't doubt for one minute that others will get caught (or will have been caught) by this. The problem is with teaser truncation. Our authors can use most html in particular they can open their post with 'table' and similar. They, of course, close their tags and all is well. However, when we go to a list view (say rendering a term in the taxonomy), a list of teasers is provided, in particular they often are the truncated 600 characters of a post. And sometimes that includes an opening 'table' tag but no closing one. Then the tpl.php etc start putting opening and closing 'Divs' around the list items. But that then gives you a result where you have an opening 'div' an opening 'table' then a closing 'div' ie overlapping tags. A few of these and the whole lot falls over.
Solutions:
a) use the module Node Teaser and have an unproblematic teaser (I'm trying this successfully).
b) ban the use of 'table' etc tags (not practical)
c) run the open 600 characters of the post through a filter that removes bad stuff prior to forming the teaser (seems the right way to go).
Hope this helps someone!
Comment #3
David Lesieur commentedRight, the issue is not directly related to Faceted Search.
Thanks for the solutions you have provided!