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 |
|---|---|
| 267 | * @since 3.9.0 |
| 268 | * |
| 269 | * @param null|bool|object $network Network value to return by path. |
| 270 | * @param string $domain The requested domain. |
| 271 | * @param string $path The requested path, in full. |
| 272 | * @param int|null $segments The suggested number of paths to consult. |
| 273 | * Default null, meaning the entire path was to be consulted. |
| 274 | * @param array $paths The paths to search for, based on $path and $segments. |
| 275 | */ |
| 276 | $pre = apply_filters( 'pre_get_network_by_path', null, $domain, $path, $segments, $paths ); |
| 277 | if ( null !== $pre ) { |
| 278 | return $pre; |
| 279 | } |
| 280 | |
| 281 | // @todo Consider additional optimization routes, perhaps as an opt-in for plugins. |
| 282 | // We already have paths covered. What about how far domains should be drilled down (including www)? |
| 283 | |
| 284 | $search_domains = "'" . implode( "', '", $wpdb->_escape( $domains ) ) . "'"; |
| 285 | |