Actions

Intercessor integrates with WordPress through actions throughout its lifecycle. When extending the plugin, prefer existing lifecycle hooks over modifying plugin core files.

For the authoritative list of available hooks, search the plugin source for do_action() and review the arguments at each call site.

Recommended practice

• Keep callbacks narrowly scoped.
• Check capabilities before administrative operations.
• Sanitize and validate incoming values.
• Avoid direct modification of Intercessor database tables when a query abstraction exists.
• Make custom behavior removable and namespaced.

TIP

The plugin's REST registration, block registration, admin menu, scheduled notifications, and settings registration all use WordPress's action system.

Version-specific hook reference

This page intentionally avoids presenting an unverified list of hook names. For Intercessor 1.1.0 extension work, identify the relevant do_action() call in the source and confirm its argument list before registering a callback.

Example pattern:

add_action( 'hook_name', 'my_callback' );

function my_callback( $value ) {
    // Custom behavior.
}

Replace hook_name and the callback signature with the exact hook documented for the Intercessor release you support.