We have released an add-on with shared functionality of all our "filter" add-ons. The reason for separating this functionality is to make it easier to maintain and to allow for more flexibility in the future.
The following fixes are included in the latest Filter Framework package:
- Fix: multiple prefix filter not working
- Fix: indexation of array-type custom fields may trigger PHP error
- Enhancement: Do not use AJAX for loading filterable list options if there are no more than 30 options
The release fixes a problem with the option
Maximum result count. If the option is set to a low number, the results might not respect the default order if items and older results may be shown. The problem does not affect the Elasticsearch back-end.
This release is due to a change in [AL] Core package regarding class extensions, which was causing some compatibility issues with other add-ons. Please upgrade if you are using [AL] Core version 1.5.5+.
This version fixes a bug appearing when admins use the option "Value display HTML" for a custom field using HTML that breaks the layout in the Active filters bar. The HTML will be stripped away now and only the raw value will be shown in the bar.
This version enhances location support using the latest upgrade of the Location custom field add-on. Now you can choose to hide the default distance unit in the filter form. From this version on, the Google API key should be specified in the Location custom field add-on options. Please verify these options after the upgrade. It also fixes a bug with the option Maximum result count that would not allow 0 as a value.
This version fixes the following PHP error when rebuilding custom fields:
Error: Call to undefined method XF\Util\Arr::arrayColumn()
The release fixes a bug, that would cause ES search error "Elasticsearch error: all shards failed". This would happen only if you have Multiple prefix search option activated, and if a user/bot manually modifies the URL to include invalid prefix IDs (which are normally numeric). This is not a security issue as an attacker would not get any error message except that searching failed.