Context

On the original legacy site bizneshelper.ru, the search is currently broken: when attempting to execute a search query, the user receives a standard Rails error We're sorry, but something went wrong..

This is a defect in the old Ruby implementation, not the new version of the site.

Goal

Understand the actual cause of the legacy search crash and ensure a working search scenario in the new implementation on haih-cms.

What to do

• Reproduce the error on a locally running copy of the legacy site.
• Check if the failure is related to Sunspot/Solr, missing index, connection configuration, or result handling in the Rails application.
• Document which content types historically participated in the search.
• Determine which search scenarios are actually needed by the user on the new site.
• Do not consider restoring the old Solr mandatory by itself: if the legacy search is only needed as a source for understanding behavior, implement the new search using the current stack.
• Test search across main public entities and typical queries.
• Provide clear behavior when there are no results and in case of a technical error.

Result

The cause of the old search crash is understood, and the new version of the site has a working and predictable search scenario.

Definition of Done

• The legacy error is reproduced and its source is identified.
• It is clear which entities should be indexed in the new search.
• Search in the new version does not depend on the old Rails/Solr circuit without explicit necessity.
• The user receives results, an empty state, or a controlled error message rather than a generic 500 page.

Constraints

Do not publish internal Solr addresses, connection secrets, production logs, and other sensitive parameters in the open task.