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 |
|---|---|
| 768 | * will be used to serve the request instead. |
| 769 | * |
| 770 | * @since 4.4.0 |
| 771 | * |
| 772 | * @param mixed $result Response to replace the requested version with. Can be anything |
| 773 | * a normal endpoint can return, or null to not hijack the request. |
| 774 | * @param WP_REST_Server $this Server instance. |
| 775 | * @param WP_REST_Request $request Request used to generate the response. |
| 776 | */ |
| 777 | $result = apply_filters( 'rest_pre_dispatch', null, $this, $request ); |
| 778 | |
| 779 | if ( ! empty( $result ) ) { |
| 780 | return $result; |
| 781 | } |
| 782 | |
| 783 | $method = $request->get_method(); |
| 784 | $path = $request->get_route(); |
| 785 | |
| 786 | foreach ( $this->get_routes() as $route => $handlers ) { |