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 |
|---|---|
| 2471 | * Fires after enqueuing block assets for both editor and front-end. |
| 2472 | * |
| 2473 | * Call `add_action` on any hook before 'wp_enqueue_scripts'. |
| 2474 | * |
| 2475 | * In the function call you supply, simply use `wp_enqueue_script` and |
| 2476 | * `wp_enqueue_style` to add your functionality to the Gutenberg editor. |
| 2477 | * |
| 2478 | * @since 5.0.0 |
| 2479 | */ |
| 2480 | do_action( 'enqueue_block_assets' ); |
| 2481 | } |
| 2482 | |
| 2483 | /** |
| 2484 | * Enqueues registered block scripts and styles, depending on current rendered |
| 2485 | * context (only enqueuing editor scripts while in context of the editor). |
| 2486 | * |
| 2487 | * @since 5.0.0 |
| 2488 | * |
| 2489 | * @global WP_Screen $current_screen WordPress current screen object. |