xF2 Add-on Resource Filter by AddonsLab 3.6.1

This version fixes a PHP error on the general search page introduced in version 3.4.0:

TypeError: Argument 1 passed to XF\Search\Search::getResultSet()

Click to expand...

This version implements compatibility with XenForo 2.2

If the filter URL is modified and the values of multiple-selection fields are changed intentionally (e.g. with an attempt to cause an error in the website or execute SQL injection), there would be a PHP error logged in the admin panel. However, this would not cause any visible errors or unexpected SQL queries. With this release, we have made sure these invalid values don't make their way to built-in XenForo functions that expect only valid values.

This version also fixes a compatibility issue with Elasticsearch 7.x versions.

The release fixes an accidental issue in version 3.1.0 including older files that caused JavaScript errors in the filter form. Please apply the version asap if you have installed the version 3.1.0. or above.

The update fixes the error logged in the Server Error - "Unsupported operand types". The error would accure in cases of a forum not having configured any filterable custom fields.

The release fixes an accidental issue in the last version including older files that caused different PHP errors. Please apply the version asap if you have installed the version 3.1.0.

In some cases number type fields are used for data that does not require number formatting (e.g. if the custom field represents years, it should not be shown as "2.020" but "2020". We have added an option that allows admins to list the IDs of such custom fields, and they will not be formatted in the output.

The release also fixes a bug, that would log a PHP error in some cases if the option "Total count indicator is active".

Important Note: If you are using several of our Filter add-ons, please disable them before applying the upgrade. Upgrade all add-ons and only after that enable the products.

The release fixes a bug with a Facet search showing the wrong number of matching results. The issue was related to Elasticsearch optimization considering only the top results, so the options that had fewer matching items would be shown as having no documents. The issue does not affect you if you are using MySQL as a search index or you are not using the Facet search option.

Fixed a PHP error:

Error: Call to undefined method XF\Mvc\Reply\Redirect::getParams() src/addons/AL/ResourceFilter/XFRM/Pub/Controller/Category.php:36

Click to expand...

The version removes an accidental dependency on Thread Filter add-on.