Views "Relevance" sort criterion not sorting by relevance

I have the same problem. If in my view for the search results I configure the sort criteria as search: relevance (descending), the actual results are sorted randomly.

I found this patch: https://www.drupal.org/files/issues/added-correct-grouping.patch but this is for D7.

I think i found the problem.

This condition in SolrHelper::addSorts() causes the problem, as the fieldname is search_api_relevance. That matches strpos($field_names[$field], 's') and $f becomes sort_search_api_relevance instead of sort.

      elseif ($new_schema_version && (strpos($field_names[$field], 't') === 0 || strpos($field_names[$field], 's') === 0)) {
        // For fulltext fields use the dedicated sort field for faster alpha
        // sorts. Use the same field for strings to sort on a normalized value.
        $f = 'sort_' . $field;
      }

Patch to follow very soon.

This patch fixed it for me. I created a new condition, that catches the "sort-by-score" case before the fulltext sort condition is met.

Apparently this is a search_api_solr issue.

Hi @dermario Thanks for contribution some coding thing to be change like variable name $f. Give some specific name.

Thank you @sumit-kumar, for the quick review. Although i am not sure, whether the variable naming of $f is the scope of this issue, i renamed it to $sort_field. Hope thats better now.

@dermario Thanks for quick response now its look great for me.

You already discovered the right part of the code. Nevertheless I want to solve the issue slightly different and prepare some further cleanup of the code in the future.
Basically the the association between "search_api_relevance" and the corresponding pseudo Solr field "score" is already in place. But the lately added match for dynamic fields starting with an "s" caused an overwrite of that association.

Looks good and works for me. The restructuring makes totally sense to me. As i introduced a kind of redundant code with my extra-condition. I applied the patch in #15, read and understood the changes and verified its correct functionality. I will put the issue to RTBC.

*Sort by asc:*

*Sort by dec:*

Just committed the patch. Thanks everyone.

Was this only for 8.x-2.x?

The issue + commit says 1.x, but I can't find this code in dev nor does the patch apply...

The code exists in 1.x and 2.x! Search for the protected function setSorts.
If you have an issue with sorts, please open a new issue.