Opensolr Changelog

Recent updates and improvements to the Opensolr platform.

Search × Apr 2026 ×

Search Apr 22, 2026

  • Fix Search Page Fix: showPicker SecurityError in Cross-Origin Iframes Silently Handled
    Fixed a JavaScript SecurityError thrown when the Opensolr search page is embedded inside a cross-origin iframe. Browsers block showPicker() calls from cross-origin frames; the call is now wrapped in a try/catch so the browser restriction is silently handled instead of surfacing as an uncaught exception that could disrupt other search functionality on the host page.
  • Fix Four Search Parameter Fixes: Wildcard Highlighting, hl.q, Stats and Currency Facets
    Fixed four search parameter bugs across all platforms. (1) Wildcard searches (*:*) no longer send any highlighting parameters to Solr — highlighting on a catch-all query is meaningless and wastes server cycles. (2) The Solr highlight query (hl.q) was incorrectly set to *:* instead of the real search terms, so highlighted snippets never matched actual keywords. (3) A hardcoded stats=true / stats.field=price_f block was attached to every query even for non-commerce indexes. (4) currency_s was hardcoded into the facet field list regardless of whether the index has that field. All four are fixed in Opensolr, the Drupal module, and the WordPress plugin.
  • Improved Locale Facet Shows Flags and Language Names Across Opensolr Search, Drupal and WordPress
    Locale facet — flags and readable names throughout the search UI. The Locale sidebar facet now shows flag emojis and language names instead of raw locale codes: hr_hr becomes 🇭🇷 Croatian, sr_sr becomes 🇷🇸 Serbian, and so on. The top-right All Locales selector panel also displays the correct country flag beside each language group. Active locale filters — whether applied from the sidebar facet or the top-right panel — appear as removable pills labelled with flag and name. Languages without a canonical country flag (e.g. Latin, constructed codes) show a 🌐 globe icon. Applied across the Opensolr search page, Drupal module, and WordPress plugin.
  • New New Lexical Only Search Mode Skips Embeddings for Pure BM25 Ranking
    New Lexical Only search mode in Search Tuning → Search Mode. Explicit opt-out from vector — no embedding API call is made, search runs straight through the lexical edismax path. Useful for deterministic BM25 ranking, avoiding embedding API latency, or users on plans without vector who want explicit control instead of the implicit server-side fallback. When selected, the Minimum Relevance Score slider auto-zeros itself (that threshold is calibrated for the combined hybrid score; a positive value would filter out every result in pure lexical mode) and a yellow note explains the coupling.

Search Apr 21, 2026

  • Fix Custom Minimum Match Values No Longer Truncated by the XSS Filter
    Fixed custom Minimum Match values not saving. Values containing the less-than character (e.g. 2<95% 5<90% 8<80%) were silently truncated to just the first number because the global XSS filter stripped the < before the value reached the save handler. The tuning form now reads the raw request body for this field — custom mm presets save and apply correctly.
  • Improved Search Page Pagination Moved Into the Results Column, Top Block Removed
    Search page pagination layout cleaned up — pagination is now rendered inside the results column instead of drifting to the left under the facet sidebar, and the redundant top pagination block (which appeared next to the "Did you mean" spellcheck line) has been removed. Pagination now lives only at the bottom of the results, aligned with the rest of the content.
  • New Search Operators Help Panel: Phrase Match, Required, and Excluded Terms
    New Search Operators help button next to the Search bar. Opens a panel explaining "phrase match", +required, and -excluded operators with examples and a note on why they matter in hybrid search. Users can now refine queries like +laptop "13 inch" -refurbished and cut through semantic noise instantly.
  • New New Minimum Relevance Score Slider Filters Low-Scoring Hybrid Search Hits
    New Minimum Relevance Score slider in Search Tuning. Drops hits whose combined lexical + vector score falls below the threshold, cleaning noise out of facet counts and result totals. Essential for hybrid search on catalog-style content — without it, numFound balloons to the entire filter set and facet counts pick up docs the user would never consider relevant. Slider moves in 0.1 increments, default 0.3, 0 disables.

Search Apr 10, 2026

  • Improved Hybrid Search Relevance: Lexical Field Boosts Zeroed in Vector Mode
    Improved hybrid search relevance — in vector hybrid mode, lexical field weight boosts are now automatically zeroed out so that semantic similarity drives the relevance ranking. Previously, even small lexical boosts could inflate scores well above the 0-1 vector range, pushing semantically relevant results down. Field weights still apply when search falls back to pure lexical mode.

Search Apr 9, 2026

Search Apr 4, 2026

Search Apr 3, 2026