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 |
|---|---|
| 261 | $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); |
| 262 | |
| 263 | /** |
| 264 | * Filters the user's drafts query string. |
| 265 | * |
| 266 | * @since 2.0.0 |
| 267 | * |
| 268 | * @param string $query The user's drafts query string. |
| 269 | */ |
| 270 | $query = apply_filters( 'get_users_drafts', $query ); |
| 271 | return $wpdb->get_results( $query ); |
| 272 | } |
| 273 | |
| 274 | /** |
| 275 | * Remove user and optionally reassign posts and links to another user. |
| 276 | * |
| 277 | * If the $reassign parameter is not assigned to a User ID, then all posts will |
| 278 | * be deleted of that user. The action {@see 'delete_user'} that is passed the User ID |
| 279 | * being deleted will be run after the posts are either reassigned or deleted. |