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 |
|---|---|
| 1553 | * Filter the ORDER BY clause in the SQL for an adjacent post query. |
| 1554 | * |
| 1555 | * The dynamic portion of the hook name, `$adjacent`, refers to the type |
| 1556 | * of adjacency, 'next' or 'previous'. |
| 1557 | * |
| 1558 | * @since 2.5.0 |
| 1559 | * |
| 1560 | * @param string $order_by The `ORDER BY` clause in the SQL. |
| 1561 | */ |
| 1562 | $sort = apply_filters( "get_{$adjacent}_post_sort", "ORDER BY p.post_date $order LIMIT 1" ); |
| 1563 | |
| 1564 | $query = "SELECT p.ID FROM $wpdb->posts AS p $join $where $sort"; |
| 1565 | $query_key = 'adjacent_post_' . md5( $query ); |
| 1566 | $result = wp_cache_get( $query_key, 'counts' ); |
| 1567 | if ( false !== $result ) { |
| 1568 | if ( $result ) |
| 1569 | $result = get_post( $result ); |
| 1570 | return $result; |
| 1571 | } |