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 |
|---|---|
| 370 | $this->query_string .= (strlen($this->query_string) < 1) ? '' : '&'; |
| 371 | if ( !is_scalar($this->query_vars[$wpvar]) ) // Discard non-scalars. |
| 372 | continue; |
| 373 | $this->query_string .= $wpvar . '=' . rawurlencode($this->query_vars[$wpvar]); |
| 374 | } |
| 375 | } |
| 376 | |
| 377 | // query_string filter deprecated. Use request filter instead. |
| 378 | if ( has_filter('query_string') ) { // Don't bother filtering and parsing if no plugins are hooked in. |
| 379 | $this->query_string = apply_filters('query_string', $this->query_string); |
| 380 | parse_str($this->query_string, $this->query_vars); |
| 381 | } |
| 382 | } |
| 383 | |
| 384 | /** |
| 385 | * Setup the WordPress Globals. |
| 386 | * |
| 387 | * The query_vars property will be extracted to the GLOBALS. So care should |
| 388 | * be taken when naming global variables that might interfere with the |