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 |
|---|---|
| 862 | * Filters the block being rendered in render_block(), before it's processed. |
| 863 | * |
| 864 | * @since 5.1.0 |
| 865 | * @since 5.9.0 The `$parent_block` parameter was added. |
| 866 | * |
| 867 | * @param array $parsed_block The block being rendered. |
| 868 | * @param array $source_block An un-modified copy of $parsed_block, as it appeared in the source content. |
| 869 | * @param WP_Block|null $parent_block If this is a nested block, a reference to the parent block. |
| 870 | */ |
| 871 | $parsed_block = apply_filters( 'render_block_data', $parsed_block, $source_block, $parent_block ); |
| 872 | |
| 873 | $context = array(); |
| 874 | |
| 875 | if ( $post instanceof WP_Post ) { |
| 876 | $context['postId'] = $post->ID; |
| 877 | |
| 878 | /* |
| 879 | * The `postType` context is largely unnecessary server-side, since the ID |
| 880 | * is usually sufficient on its own. That being said, since a block's |