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 |
|---|---|
| 2367 | * Fires after enqueuing block assets for both editor and front-end. |
| 2368 | * |
| 2369 | * Call `add_action` on any hook before 'wp_enqueue_scripts'. |
| 2370 | * |
| 2371 | * In the function call you supply, simply use `wp_enqueue_script` and |
| 2372 | * `wp_enqueue_style` to add your functionality to the Gutenberg editor. |
| 2373 | * |
| 2374 | * @since 5.0.0 |
| 2375 | */ |
| 2376 | do_action( 'enqueue_block_assets' ); |
| 2377 | } |
| 2378 | |
| 2379 | /** |
| 2380 | * Applies a filter to the list of style nodes that comes from WP_Theme_JSON::get_style_nodes(). |
| 2381 | * |
| 2382 | * This particular filter removes all of the blocks from the array. |
| 2383 | * |
| 2384 | * We want WP_Theme_JSON to be ignorant of the implementation details of how the CSS is being used. |
| 2385 | * This filter allows us to modify the output of WP_Theme_JSON depending on whether or not we are |