jreviews:search.parse_request_filters
Filters the parsed custom field filter payload extracted from a search request. Use this to inject derived field filters, drop unsupported params, or adjust AND/OR match flags before downstream consumers use them.
You need to have a working knowledge of Hooks before you get started.
Fires after search request field filters are parsed and sanitized
Parameters
| Name | Type | Description |
|---|---|---|
$parsed |
array |
{ @type array $activeFilters Active `jr_*` field filters parsed from the request @type array $matchParams Per-field AND/OR match flags parsed from `match_*` } |
$request |
\FWD\Illuminate\Http\Request |
The current request |
Boilerplate Code
Use the boilerplate code to start using the filter, and add your own logic to modify the first argument and return it.
fwd_add_filter('jreviews:search.parse_request_filters', function($parsed, $request)
{
// Your code here
return $parsed;
}, 20, 2);
The , 20, N after your callback are the hook priority and the number of arguments your callback accepts. By default, a hook passes your callback only its first argument; for a filter, that is the value being filtered, so a simple function($value) { ... } needs nothing extra. If your callback declares more parameters, such as function($value, $listing) { ... }, you must add N (the parameter count, 2 here). Because N is the fourth argument to fwd_add_filter() or fwd_add_action(), you must also pass the priority (20 is the default). Leaving these off when your callback expects extra parameters causes a Too few arguments to function ... fatal error.
Source Files
app/Actions/ResolveFilterContextAction.php