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 |
|---|---|
| 210 | * |
| 211 | * @since 2.0.0 |
| 212 | * |
| 213 | * @param int $user_id User ID. |
| 214 | * @return array |
| 215 | */ |
| 216 | function get_users_drafts( $user_id ) { |
| 217 | global $wpdb; |
| 218 | $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); |
| 219 | $query = apply_filters('get_users_drafts', $query); |
| 220 | return $wpdb->get_results( $query ); |
| 221 | } |
| 222 | |
| 223 | /** |
| 224 | * Remove user and optionally reassign posts and links to another user. |
| 225 | * |
| 226 | * If the $reassign parameter is not assigned to an User ID, then all posts will |
| 227 | * be deleted of that user. The action 'delete_user' that is passed the User ID |
| 228 | * being deleted will be run after the posts are either reassigned or deleted. |