Opensolr Changelog — Recent Updates & Improvements

Search Apr 22, 2026

Fix 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 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.

Fix 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.

Fix Fixed Query Elevation controls not appearing on the hosted search page. Token-based authentication now accounts for CAPTCHA verification time, and elevation settings take effect immediately after toggling (previously required up to 10 minutes due to caching).

Fix Fixed search result highlighting — switched to a more reliable highlighter that correctly highlights keywords in short fields like titles. Also added text_t (structured text) to highlighted fields for richer snippets.