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 |
|---|---|
| 2343 | * Fires after enqueuing block assets for both editor and front-end. |
| 2344 | * |
| 2345 | * Call `add_action` on any hook before 'wp_enqueue_scripts'. |
| 2346 | * |
| 2347 | * In the function call you supply, simply use `wp_enqueue_script` and |
| 2348 | * `wp_enqueue_style` to add your functionality to the Gutenberg editor. |
| 2349 | * |
| 2350 | * @since 5.0.0 |
| 2351 | */ |
| 2352 | do_action( 'enqueue_block_assets' ); |
| 2353 | } |
| 2354 | |
| 2355 | /** |
| 2356 | * Enqueues the global styles defined via theme.json. |
| 2357 | * |
| 2358 | * @since 5.8.0 |
| 2359 | */ |
| 2360 | function wp_enqueue_global_styles() { |
| 2361 | $separate_assets = wp_should_load_separate_core_block_assets(); |