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 |
|---|---|
| 470 | if ( has_filter( 'query_string' ) ) { // Don't bother filtering and parsing if no plugins are hooked in. |
| 471 | /** |
| 472 | * Filter the query string before parsing. |
| 473 | * |
| 474 | * @since 1.5.0 |
| 475 | * @deprecated 2.1.0 Use 'query_vars' or 'request' filters instead. |
| 476 | * |
| 477 | * @param string $query_string The query string to modify. |
| 478 | */ |
| 479 | $this->query_string = apply_filters( 'query_string', $this->query_string ); |
| 480 | parse_str($this->query_string, $this->query_vars); |
| 481 | } |
| 482 | } |
| 483 | |
| 484 | /** |
| 485 | * Set up the WordPress Globals. |
| 486 | * |
| 487 | * The query_vars property will be extracted to the GLOBALS. So care should |
| 488 | * be taken when naming global variables that might interfere with the |