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 |
|---|---|
| 1548 | return $response; |
| 1549 | } |
| 1550 | $parsed_blocks = parse_blocks( $response->data['content']['raw'] ); |
| 1551 | $content = block_core_navigation_insert_hooked_blocks( $parsed_blocks, $post ); |
| 1552 | |
| 1553 | // Remove mock Navigation block wrapper. |
| 1554 | $content = block_core_navigation_remove_serialized_parent_block( $content ); |
| 1555 | |
| 1556 | $response->data['content']['raw'] = $content; |
| 1557 | $response->data['content']['rendered'] = apply_filters( 'the_content', $content ); |
| 1558 | |
| 1559 | return $response; |
| 1560 | } |
| 1561 | |
| 1562 | /* |
| 1563 | * Before adding our filter, we verify if it's already added in Core. |
| 1564 | * However, during the build process, Gutenberg automatically prefixes our functions with "gutenberg_". |
| 1565 | * Therefore, we concatenate the Core's function name to circumvent this prefix for our check. |
| 1566 | */ |