jreviews:permission:listing.allows_html_in_summary_description
Filters whether a user has permission to include HTML in listing summary and description fields. Controls access to WYSIWYG editor.
You need to have a working knowledge of Hooks before you get started.
Fires when checking if WYSIWYG editor should be shown or if HTML input should be accepted
Parameters
| Name | Type | Description |
|---|---|---|
$canIncludeHtml |
bool |
Whether the user can include HTML (editors and users in WYSIWYG-enabled groups by default) |
$user |
\JReviews\App\Models\User |
The user attempting to use HTML |
$listing |
\JReviews\App\Models\Listing |
The listing being created or edited |
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:permission:listing.allows_html_in_summary_description', function($canIncludeHtml, $user, $listing)
{
// Your code here
return $canIncludeHtml;
}, 20, 3);
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/Policies/ListingPolicy.php