SearchStax Site Search release notes for September 4, 2025 include Hosted Search version selection, /emselect parameter handling updates, and login and navigation performance improvements.
Highlights
- Hosted Search Experience: choose a specific library version or keep automatic updates. Reduces upgrade risk and gives you control over when to take changes.
- Performance: faster login and navigation.
- Search API: updated
/emselectparameter handling (last value wins). If you parse arrays fromresponseHeader.params, review your code.
Added
[Versioning] Hosted Search Version Selection
You can pin your Hosted Search page to an exact library version (for example, v4.3.2) instead of using the generic v3/v4 tags.
Impact
Stable behavior across releases. No unexpected UI or API changes from automatic updates.
Action
Optional. When you copy the Hosted Search page or set up Headless/UX JS, reference a specific version if you want stability. If you want the latest changes automatically, continue using v3/v4.
For example, to pin the Hosted Search Experience to a specific release, edit the script/link URLs to use a full semantic tag, like /studio/-js/v4.1.5. Using a major version alias, like v4, keeps automatic updates, while using an exact version number locks the experience to that release.
Docs
- Samples (npm approach for v4): https://github.com/searchstax/searchstudio-ux-samples/tree/master/pages/js
- Changelog (v3): https://static.searchstax.com/studio-js/v3/CHANGELOG.md
- Changelog (v4): https://static.searchstax.com/studio-js/v4/CHANGELOG.md
Changed
- Hosted page includes a small version notice at the top and a comment near the library includes to indicate the exact version in use. You can remove the notice in your own implementation.
[Breaking] Search API — /emselect Parameter Handling
To support profile-level customizations (rows, Result Fields, Faceting, Spellcheck), duplicate request parameters are now deduplicated and the last value wins. The value in responseHeader.params. is now a single string, not an array, when duplicates are present.
Example
The profile default is rows=10. The request uses rows=15. The array ["10","15"] becomes "15", and 15 results are displayed.
Impact
Integrations that expected arrays from responseHeader.params may break.
Action
Avoid sending duplicate params; update any parsing logic to handle a single value. This matches default Solr behavior.
Performance & Scalability
[Performance] Login and Navigation
Logging in and navigating between pages in the SearchStax Site Search UI is now faster.
Impact
Faster login and page load.
Action
None.
Rollout
- Target date: Friday, September 5, 2025.
- Scope: Hosted Search Experience (Legacy + Headless JS); Console (Plans/Entitlements); Search API (/emselect) parameter handling.
Known Issues
- None expected for existing implementations. If you rely on automatic updates today, no action is required.