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 |
|---|---|
| 2012 | * @type array $attrs Attributes from block comment delimiters. |
| 2013 | * @type array[] $innerBlocks List of inner blocks. An array of arrays that |
| 2014 | * have the same structure as this one. |
| 2015 | * @type string $innerHTML HTML from inside block comment delimiters. |
| 2016 | * @type array $innerContent List of string fragments and null markers where |
| 2017 | * inner blocks were found. |
| 2018 | * } |
| 2019 | * @param WP_Block|null $parent_block If this is a nested block, a reference to the parent block. |
| 2020 | */ |
| 2021 | $parsed_block = apply_filters( 'render_block_data', $parsed_block, $source_block, $parent_block ); |
| 2022 | |
| 2023 | $context = array(); |
| 2024 | |
| 2025 | if ( $post instanceof WP_Post ) { |
| 2026 | $context['postId'] = $post->ID; |
| 2027 | |
| 2028 | /* |
| 2029 | * The `postType` context is largely unnecessary server-side, since the ID |
| 2030 | * is usually sufficient on its own. That being said, since a block's |