WP hooks navigation: Home/browse • Actions index • Filters index
To save our bandwidth, we show only a snippet of code around each occurence of the hook. View complete file in SVN (without highlighting).
The best way to understand what a hook does is to look at where it occurs in the source code.
do_action( "hook_name" )apply_filters( "hook_name", "what_to_filter" ).Remember, this hook may occur in more than one file. Moreover, the hook's context may change from version to version.
| Line | Code |
|---|---|
| 650 | * if unscheduling one or more events fails. |
| 651 | * |
| 652 | * @since 5.1.0 |
| 653 | * @since 5.7.0 The `$wp_error` parameter was added, and a `WP_Error` object can now be returned. |
| 654 | * |
| 655 | * @param null|int|false|WP_Error $pre Value to return instead. Default null to continue unscheduling the hook. |
| 656 | * @param string $hook Action hook, the execution of which will be unscheduled. |
| 657 | * @param bool $wp_error Whether to return a WP_Error on failure. |
| 658 | */ |
| 659 | $pre = apply_filters( 'pre_unschedule_hook', null, $hook, $wp_error ); |
| 660 | |
| 661 | if ( null !== $pre ) { |
| 662 | if ( $wp_error && false === $pre ) { |
| 663 | return new WP_Error( |
| 664 | 'pre_unschedule_hook_false', |
| 665 | __( 'A plugin prevented the hook from being cleared.' ) |
| 666 | ); |
| 667 | } |
| 668 | |