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 |
|---|---|
| 275 | $query = $wpdb->prepare("SELECT ID, post_title FROM $wpdb->posts WHERE post_type = 'post' AND post_status = 'draft' AND post_author = %d ORDER BY post_modified DESC", $user_id); |
| 276 | |
| 277 | /** |
| 278 | * Filters the user's drafts query string. |
| 279 | * |
| 280 | * @since 2.0.0 |
| 281 | * |
| 282 | * @param string $query The user's drafts query string. |
| 283 | */ |
| 284 | $query = apply_filters( 'get_users_drafts', $query ); |
| 285 | return $wpdb->get_results( $query ); |
| 286 | } |
| 287 | |
| 288 | /** |
| 289 | * Remove user and optionally reassign posts and links to another user. |
| 290 | * |
| 291 | * If the $reassign parameter is not assigned to a User ID, then all posts will |
| 292 | * be deleted of that user. The action {@see 'delete_user'} that is passed the User ID |
| 293 | * being deleted will be run after the posts are either reassigned or deleted. |