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 |
---|---|
3535 |
|
3536 | /** |
3537 | * Fires once the theme has switched in the Customizer, but before settings |
3538 | * have been saved. |
3539 | * |
3540 | * @since 3.4.0 |
3541 | * |
3542 | * @param WP_Customize_Manager $manager WP_Customize_Manager instance. |
3543 | */ |
3544 | do_action( 'customize_save', $this ); |
3545 |
|
3546 | /* |
3547 | * Ensure that all settings will allow themselves to be saved. Note that |
3548 | * this is safe because the setting would have checked the capability |
3549 | * when the setting value was written into the changeset. So this is why |
3550 | * an additional capability check is not required here. |
3551 | */ |
3552 | $original_setting_capabilities = array(); |
3553 | foreach ( $changeset_setting_ids as $setting_id ) { |