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 |
|---|---|
| 785 | * they are the default. For WordPress sites that have heavy site management in the Customizer |
| 786 | * by multiple users then branching changesets should be enabled by means of this filter. |
| 787 | * |
| 788 | * @since 4.9.0 |
| 789 | * |
| 790 | * @param bool $allow_branching Whether branching is allowed. If `false`, the default, |
| 791 | * then only one saved changeset exists at a time. |
| 792 | * @param WP_Customize_Manager $wp_customize Manager instance. |
| 793 | */ |
| 794 | $this->branching = apply_filters( 'customize_changeset_branching', $this->branching, $this ); |
| 795 | |
| 796 | return $this->branching; |
| 797 | } |
| 798 | |
| 799 | /** |
| 800 | * Get the changeset UUID. |
| 801 | * |
| 802 | * @since 4.7.0 |
| 803 | * @see WP_Customize_Manager::establish_loaded_changeset() |