jreviews:listing_form.after_field:{:name}

Allows injecting custom HTML/content immediately after a specific custom field input in the listing form.

You need to have a working knowledge of Hooks before you get started.

#Parameters

#Variations

This dynamic hook fires for each of the following variations. The {:name} placeholder in the hook name is replaced with one of these values:

For example, to target the - `jreviews:listing_form.after_field:jr_city` - After 'jr_city' field - `jreviews:listing_form.after_field:jr_phone` - After 'jr_phone' field - Pattern follows field name exactly variation, you would use:

fwd_add_action('jreviews:listing_form.after_field:- `jreviews:listing_form.after_field:jr_city` - After 'jr_city' field - `jreviews:listing_form.after_field:jr_phone` - After 'jr_phone' field - Pattern follows field name exactly', function($field, $listing, $fieldGroups)
{
    // Your code here
}, 20, 3);

#Boilerplate Code

Use the boilerplate code to start using the action, and add your own logic or echo output.

fwd_add_action('jreviews:listing_form.after_field:{:name}', function($field, $listing, $fieldGroups)
{
    // Execute action or echo output
}, 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

• resources/views/site/components/listing/form.blade.php
• resources/views/cp/components/listing/content-tab.blade.php