Actions

kickbox_gf_init

Action kickbox_gf_init fires when Gravity Forms Kickbox Add-On has been initialized.

kickbox_gf_cached_verification

Action kickbox_gf_cached_verification fires when a verification got retrieved from the Database as a cached one.

Params:

Name	Type	Description
$email	string	Submitted value
$cached_verification	array	Stored verification for the $email

Example:

add_action( 'kickbox_gf_cached_verification', 'my_func', 10, 2 );

function my_func( $email, $cached_verification ) {
    // use $email or $cached_verification somehow
}

kickbox_gf_verification_interpreted

Action kickbox_gf_verification_interpreted fires when a verification got interpreted in accordance with the specified configuration settings. Provides access to $verification and $interpretation. NB: Fires for invalid verifications too, e.g. when Kickbox responds with the Insufficient balance error or HTTP-request fails.

Params:

Name	Type	Description
$verification	array	Verification
$interpretation	array	Interpretation of the verification

Example:

add_action( 'kickbox_gf_verification_interpreted', 'my_func', 10, 2 );

function my_func( $verification, $interpretation ) {
    // use $verification or $interpretation somehow
}

kickbox_gf_verifications_before_pruning

Action kickbox_gf_verifications_before_pruning fires when the CRON-job responsible for pruning cached verifications received stored ones from the database.

Params:

Name	Type	Description
$stored_verifications	array	Cached email verifications

kickbox_gf_verifications_pruned

Action kickbox_gf_verifications_pruned fires when the CRON-job responsible for pruning cached verifications pruned old verifications and put fresh ones to the database.

Params:

Name	Type	Description
$stored_verifications	array	Cached email verifications

kickbox_gf_verification_cached

Action kickbox_gf_verification_cached fires when a verification has been saved in the database.

Params:

Name	Type	Description
$verification_to_store	array	Filtered item that was saved