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 |
|---|---|
| 3515 | |
| 3516 | /** |
| 3517 | * Fires once the theme has switched in the Customizer, but before settings |
| 3518 | * have been saved. |
| 3519 | * |
| 3520 | * @since 3.4.0 |
| 3521 | * |
| 3522 | * @param WP_Customize_Manager $manager WP_Customize_Manager instance. |
| 3523 | */ |
| 3524 | do_action( 'customize_save', $this ); |
| 3525 | |
| 3526 | /* |
| 3527 | * Ensure that all settings will allow themselves to be saved. Note that |
| 3528 | * this is safe because the setting would have checked the capability |
| 3529 | * when the setting value was written into the changeset. So this is why |
| 3530 | * an additional capability check is not required here. |
| 3531 | */ |
| 3532 | $original_setting_capabilities = array(); |
| 3533 | foreach ( $changeset_setting_ids as $setting_id ) { |