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 |
|---|---|
| 428 | * unscheduled (zero if no events were registered with the hook) or false |
| 429 | * if unscheduling one or more events fails. |
| 430 | * |
| 431 | * @since 5.1.0 |
| 432 | * |
| 433 | * @param null|int|false $pre Value to return instead. Default null to continue unscheduling the event. |
| 434 | * @param string $hook Action hook, the execution of which will be unscheduled. |
| 435 | * @param array $args Arguments to pass to the hook's callback function. |
| 436 | */ |
| 437 | $pre = apply_filters( 'pre_clear_scheduled_hook', null, $hook, $args ); |
| 438 | if ( null !== $pre ) { |
| 439 | return $pre; |
| 440 | } |
| 441 | |
| 442 | /* |
| 443 | * This logic duplicates wp_next_scheduled(). |
| 444 | * It's required due to a scenario where wp_unschedule_event() fails due to update_option() failing, |
| 445 | * and, wp_next_scheduled() returns the same schedule in an infinite loop. |
| 446 | */ |