Skip to content
iMEMBER360 Logo iMEMBER360 Documentation

Hooks and Filters

Hooks and filters allow you to extend and customize iMember360 functionality by running your own code at specific points during execution.

Action Hooks

Section titled “Action Hooks”

Action hooks allow you to execute custom code when specific events occur.

i4w_authenticated_login – Run your own code immediately after a user has authenticated during login.

This hook allows you to run your own code immediately after a user (either a local or an Keap-based subscriber) has authenticated during the login process.

iMember360 passes the WordPress user object and an array containing all contact record fields for the person who just logged in.

View Documentation
i4w_authenticated_remote_login – Run your own code immediately after an Keap-based subscriber has auth…

This hook allows you to run your own code immediately after an Keap-based subscriber has authenticated during the login process.

iMember360 passes the WordPress user object and an array containing the contact record fields for the person who just logged in.

View Documentation
i4w_wp_logout – Run your own code immediately before WordPress logout actions.

This hook allows you to run your own code immediately before any actions associated with the standard WordPress “wp_logout” action hook.

View Documentation
i4w_loaded – Run your code as soon as iMember360 is completely initialized.

This hook enables you to run your code as soon as iMember360 is completely initialized.

View Documentation
i4w_insert_post – Run your code safely after a page/post has been inserted.

This hook enables you to safely run your code after a page/post has been inserted.

iMember360 passes the post ID, the post object, and a flag indicating whether this is an insert or update.

View Documentation
i4w_update_post – Run your code safely after a page/post has been updated.

This hook enables you to safely run your code after a page/post has been updated.

iMember360 passes the post ID, the post object, and a flag indicating whether this is an insert or update.

View Documentation
i4w_saved_post – Run your code safely after a page/post has been inserted or updated.

This hook enables you to safely run your code after a page/post has been inserted or updated.

iMember360 passes the post ID, the post object, and a flag indicating whether this is an insert or update.

View Documentation

Filter Hooks

Section titled “Filter Hooks”

Filter hooks allow you to modify data before it is used.

i4w_login_redirect – Influence and manipulate the redirect URL applied when a user logs in.

This filter hook enables you to influence and manipulate the “redirect” URL that is applied each time a user logs in.

By using this filter hook, you will be able to override the plugin’s default behavior.

View Documentation
i4w_alternate_role – Influence and manipulate the WordPress role for users with certain Keap tags.

This hook enables you to influence and manipulate the WordPress role (administrator, moderator, editor, etc) for users with certain Keap tags.

If this hook is used, the WordPress user role will be updated each time the user logs in, as well as when the “i4w_genpass” module is used.

View Documentation
i4w_display_name – Influence and manipulate the WordPress ‘display_name’ field when a user is first created.

This hook enables you to influence and manipulate the WordPress field ‘display_name’ when the user is first created.

Unlike the “i4w_alternate_role” hook, this setting doesn’t get updated each time a user logs. The hook is only called once upon initial login.

View Documentation
i4w_nickname – Influence and manipulate the WordPress ‘nickname’ field when a user is first created.

This filter hook enables you to influence and manipulate the WordPress field ‘nickname’ when the user is first created.

Unlike the “i4w_alternate_role” hook, this setting doesn’t get updated each time a user logs. The hook is only called once upon initial login.

View Documentation
i4w_nicename – Influence and manipulate the WordPress ‘user_nicename’ field when a user is first created.

This filter hook enables you to influence and manipulate the WordPress field ‘user_nicename’ when the user is first created.

Unlike the “i4w_alternate_role” hook, this setting doesn’t get updated each time a user logs. The hook is only called once upon initial login.

View Documentation
i4w_excerpt – Apply your own methods to generate an excerpt.

This filter hook enables you to apply your own methods to generate an excerpt.

View Documentation
i4w_password_send_subject – Change the default “Send Password” email subject on the fly.

This filter hook enables you to change the default “Send Password” message subject on the fly through a filter.

If this hook is used, the email subject returned by your filter function will override the default text.

View Documentation
i4w_password_send_body – Change the default “Send Password” email body on the fly.

This filter hook enables you to change the default “Send Password” message body on the fly through a filter.

If this hook is used, the email body returned by your filter function will override the default text.

View Documentation
i4w_password_send_template – Change or assign an Keap email template ID on the fly.

This hook enables you to change or assign an Keap email template ID on the fly through a filter.

If this hook is used, a different email template will be used to send the mail out.

View Documentation