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 |
|---|---|
| 984 | if ( $this->query_vars['number'] && ! $this->query_vars['no_found_rows'] ) { |
| 985 | /** |
| 986 | * Filters the query used to retrieve found comment count. |
| 987 | * |
| 988 | * @since 4.4.0 |
| 989 | * |
| 990 | * @param string $found_comments_query SQL query. Default 'SELECT FOUND_ROWS()'. |
| 991 | * @param WP_Comment_Query $comment_query The `WP_Comment_Query` instance. |
| 992 | */ |
| 993 | $found_comments_query = apply_filters( 'found_comments_query', 'SELECT FOUND_ROWS()', $this ); |
| 994 | |
| 995 | $this->found_comments = (int) $wpdb->get_var( $found_comments_query ); |
| 996 | } |
| 997 | } |
| 998 | |
| 999 | /** |
| 1000 | * Fetch descendants for located comments. |
| 1001 | * |
| 1002 | * Instead of calling `get_children()` separately on each child comment, we do a single set of queries to fetch |