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 |
|---|---|
| 676 | |
| 677 | /** |
| 678 | * Filters the block being rendered in render_block(), before it's processed. |
| 679 | * |
| 680 | * @since 5.1.0 |
| 681 | * |
| 682 | * @param array $parsed_block The block being rendered. |
| 683 | * @param array $source_block An un-modified copy of $parsed_block, as it appeared in the source content. |
| 684 | */ |
| 685 | $parsed_block = apply_filters( 'render_block_data', $parsed_block, $source_block ); |
| 686 | |
| 687 | $context = array(); |
| 688 | |
| 689 | if ( $post instanceof WP_Post ) { |
| 690 | $context['postId'] = $post->ID; |
| 691 | |
| 692 | /* |
| 693 | * The `postType` context is largely unnecessary server-side, since the ID |
| 694 | * is usually sufficient on its own. That being said, since a block's |