Thanks @chetan-11, there some additional fixes to make this play nicely with php v8.2.
This module is not working with facets v2.0.6 in Drupal v10.1.5. Found another solution (Replace display values), using the ISO-3166 country list.
Thanks for the plugin @rgpublic. I also need the facility to show the word count and enforce a hard limit.
Thanks @finn-lewis, seems to me that search_api is the logical place to fix this.
We've tested with 'Fallback to multiValued field types' enabled and disabled and the error still appears with the unpatched module.
Thanks for the input @mkalkbrenner. In our case the date boost works by using search_api's aggregated field mechanism to select the last encountered value of either created or field_date_published (a field that is present only on certain specific entity types, so if present the aggregate field takes its value). So the resulting dm_field_sort_date is a single-valued field, and the data model is sound for our purposes. The underlying issue seems to be that fields are given a dm_ prefix, regardless of whether they are actually multi-valued or not. A solution might be for the aggregated field tool to name and type fields according to their cardinality.
This resolves the issue we were having with the boost processor – can we get the MR approved?