The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Took a while to trace this one down, but the root cause is the naming convention used to identify searcher info for the Facet API.
Currently this is apachesolr@<env_id>. However, this key will end up being used as part of the id on the unordered list for the resulting facet block. This is problematic because jQuery (at least the version that ships with D6) cannot locate an id with an "@" in it, so the full list of facets is always displayed. (There may be additional JS problems related to this that I didn't happen onto.)
Frankly, I'm not sure where this should be fixed. Should Apache Solr Search Integration change the searcher id? Or should the Facet API account for the fact that a module using its hooks might supply a searcher identifier with problematic characters?
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | searcher-html-ids-1918452-2.patch | 636 bytes | kevin.dutra |
Comments
Comment #1
kevin.dutra commentedThe more I think about this, the more I think that you shouldn't rely on other contrib modules to know that their searcher identifier should conform to W3C standards for ids, so I think the burden is on the Facet API module.
Comment #2
kevin.dutra commentedHere's one way it might be done. In D7, this would be done with
drupal_clean_css_identifier(), which doesn't exist in D6.Comment #3
voidberg commentedI am closing this as #1892192: Block deltas contains @ character and not a hash also fixes this issue.
Comment #3.0
voidberg commentedJust making a slight tweak