jreviews:response_content
Filters the final response body immediately before headers and content are sent to the browser. Use this to post-process rendered HTML for modern routes, mirroring the legacy `after_filter_output` behavior.
You need to have a working knowledge of Hooks before you get started.
Fires inside the sendAndContinue response macro immediately before the response is sent
Parameters
| Name | Type | Description |
|---|---|---|
$content |
string |
The current response content |
$context |
array |
{ @type \FWD\Illuminate\Http\Response $response The response instance being sent @type \Illuminate\Foundation\Application $app The application container @type string|null $route The current route name, if available } |
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:response_content', function($content, $context)
{
// Your code here
return $content;
}, 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/Providers/BootstrapProvider.php