Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.for example drupal tid:3 will show up as just drupal in the search result page.
Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.for example drupal tid:3 will show up as just drupal in the search result page.
Comments
Comment #1
robertdouglass commentedThis is a feature, not a bug, I think. I specifically take the fields out of the search box and leave only the search terms. The fields are stored within the $query object, so all of the facet links have the fields in them, as well as the URL. The search box gets mighty cluttered if all the faceting and sorting information gets stuck in there.
Does this make sense? Does anybody have complaints or suggestions on this topic?
Comment #2
janusman commentedIt's all in what constitutes good feedback.
<IMO>
If the user typed in a command, that should be kept in the search box, in lieu of a "Your current search" block. (I opened that issue some time back)
If the user clicked on facets, that interface element should change, and not put that facet command equivalent (e.g.: tid:123) in the search box, as the user did not type that in.
</IMO>
There is the problem of deciding if there should be an always-clear search box that further filters the search (i'd put that in a block also, "Filter by word"... and if I were designing the site i'd put that close to the other Filter by... blocks). The Faceted_search module always clears the only box and offers a radio button to either restart the search or filter further by what's typed in that query box...
Comment #3
robertdouglass commentedGood feedback from janusman, but I'm not inclined to fix this right now. I'd be more interested in the "Your current search" block as a compromise.