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 |
|---|---|
| 3666 | * will be reversed for two actions added at priority 10, resulting in |
| 3667 | * the core settings no longer being available as expected to themes/plugins. |
| 3668 | * So the following manually calls the method that registers the core |
| 3669 | * settings up front before doing the action. |
| 3670 | */ |
| 3671 | remove_action( 'customize_register', array( $wp_customize, 'register_controls' ) ); |
| 3672 | $wp_customize->register_controls(); |
| 3673 | |
| 3674 | /** This filter is documented in wp-includes/class-wp-customize-manager.php */ |
| 3675 | do_action( 'customize_register', $wp_customize ); |
| 3676 | } |
| 3677 | $wp_customize->_publish_changeset_values( $changeset_post->ID ); |
| 3678 | |
| 3679 | /* |
| 3680 | * Trash the changeset post if revisions are not enabled. Unpublished |
| 3681 | * changesets by default get garbage collected due to the auto-draft status. |
| 3682 | * When a changeset post is published, however, it would no longer get cleaned |
| 3683 | * out. This is a problem when the changeset posts are never displayed anywhere, |
| 3684 | * since they would just be endlessly piling up. So here we use the revisions |