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 |
---|---|
368 | * |
369 | * @since 3.9.0 |
370 | * |
371 | * @param int|null $segments The number of path segments to consider. WordPress by default looks at |
372 | * one path segment. The function default of null only makes sense when you |
373 | * know the requested path should match a network. |
374 | * @param string $domain The requested domain. |
375 | * @param string $path The requested path, in full. |
376 | */ |
377 | $segments = apply_filters( 'network_by_path_segments_count', $segments, $domain, $path ); |
378 |
|
379 | if ( ( null !== $segments ) && count( $path_segments ) > $segments ) { |
380 | $path_segments = array_slice( $path_segments, 0, $segments ); |
381 | } |
382 |
|
383 | while ( count( $path_segments ) ) { |
384 | $paths[] = '/' . implode( '/', $path_segments ) . '/'; |
385 | array_pop( $path_segments ); |
386 | } |