In #3523946: Support to be able to select different relevancy models in different views we introduced the functionality of overriding the SearchStax relevance model to use for searches on a per-view basis. When a non-default relevance model is selected for a view, this adds a model parameter to all /emselect requests for that view.
However, while the documentation clearly states that model should be the model name, our code incorrectly passed the model ID instead, which means that the parameter will not have any effect.
The code should be fixed to send the model name, not the ID, as the model parameter.
We will also need some code to migrate from existing settings (which store the ID) to the new settings – which is unfortunately not trivial as we don’t have the necessary information (the ID <-> name mapping) locally in the Drupal site.
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #4
drunken monkeyA merge request fixing this problem has been merged to HEAD where it will be tested.
Unfortunately, the fix requires manual intervention for all sites that have already configured relevance models for some views, as detailed in this change record.