listingresources:permission:resource.delete
Allows filtering whether a user can delete a resource. By default, editors and resource owners in allowed groups can delete.
You need to have a working knowledge of Hooks before you get started.
Fires when checking if user can delete a resource, before deletion is executed
Parameters
| Name | Type | Description |
|---|---|---|
$canDelete |
bool |
Whether user can delete the resource (default based on ownership and configuration) |
$user |
\JReviews\App\Models\User |
The user attempting to delete the resource |
$resource |
\JReviews\Addons\ListingResources\App\Models\ListingResource |
The resource being deleted |
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('listingresources:permission:resource.delete', function($canDelete, $user, $resource)
{
// Your code here
return $canDelete;
}, 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/ListingResourcePolicy.php