Contents
Hooks - Plugixa Team
The plugin is built so the paid layouts register themselves through the same seam a third party would use. That means the extension points are real ones, exercised by the product itself.
Layouts
add_filter( 'plugixateam_available_layouts', function ( array $layouts ) {
$layouts[] = 'my-layout';
return $layouts;
} );
add_filter( 'plugixateam_layout_template', function ( string $located, string $style ) {
return $style === 'my-layout' ? __DIR__ . '/templates/my-layout.php' : $located;
}, 10, 2 );
This is exactly how the Pro layouts are added. A layout that registers itself this way appears in the view editor alongside the built-in ones.
Assets and pagination
do_action( 'plugixateam_enqueue_layout_assets', $layout_style, $view_config );
apply_filters( 'plugixateam_no_pagination_layouts', $layouts );
The first fires when a layout renders, so a layout can load only its own CSS and JS. The second lets a layout opt out of pagination, which the carousel and the filter layout both do because they page themselves.
Member output
do_action( 'plugixateam_member_extra_fields', $member, $display );
Fires inside a member card, which is where custom fields are rendered. It is the place to add your own markup per person without replacing a template.
A note on templates
Templates can be overridden by pointing plugixateam_layout_template at your own
file. Prefer that to editing the plugin’s, which an update replaces.