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 |
|---|---|
| 1585 | * The dynamic portion of the hook name, `$adjacent`, refers to the type |
| 1586 | * of adjacency, 'next' or 'previous'. |
| 1587 | * |
| 1588 | * @since 2.5.0 |
| 1589 | * |
| 1590 | * @param string $join The JOIN clause in the SQL. |
| 1591 | * @param bool $in_same_term Whether post should be in a same taxonomy term. |
| 1592 | * @param array $excluded_terms Array of excluded term IDs. |
| 1593 | */ |
| 1594 | $join = apply_filters( "get_{$adjacent}_post_join", $join, $in_same_term, $excluded_terms ); |
| 1595 | |
| 1596 | /** |
| 1597 | * Filter the WHERE clause in the SQL for an adjacent post query. |
| 1598 | * |
| 1599 | * The dynamic portion of the hook name, `$adjacent`, refers to the type |
| 1600 | * of adjacency, 'next' or 'previous'. |
| 1601 | * |
| 1602 | * @since 2.5.0 |
| 1603 | * |