This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
customize_save_after action
Fires after Customize settings have been saved.
To use customize_save_after action, you first need to register it using add_action. You can write this code into functions.php of your activated theme or in a custom WordPress Plugin.
At WePlugins, we always prefer to create a custom WordPress Plugin while using hooks to ensure nothing breaks when you update your WordPress Theme in the future.
In the below live example, we have defined a function weplugins_execute_on_customize_save_after_event which takes one parameter and is registered using add_action. The first parameter customize_save_after is the name of the hook, the second parameter weplugins_execute_on_customize_save_after_event is the name of the function that needs to be called, the third parameter is the priority of calling the hook if the same hook is used multiple times, and the last parameter is the number of arguments (if any) to be passed in the registered function.
Sometimes, you have to remove a registered hook, so you can use remove_action to remove the customize_save_after action.
Parameters
- $manager : (WP_Customize_Manager) WP_Customize_Manager instance.
Below is the one parameter required to use this hook.
Live Example
do_action( 'customize_save_after', WP_Customize_Manager $manager )
Below is an example of how you can use this hook.
Example 1: Basic Usage
This example demonstrates a simple function attached to the customize_save_after hook.
function weplugins_execute_on_customize_save_after_event($manager){ // Code to execute when the customize_save_after action occurs. } // add the action add_action( "customize_save_after", "weplugins_execute_on_customize_save_after_event" , 10, 1);
Example 2: Logging Customizer Changes
This example logs the changes made in the customizer to a custom log file.
function weplugins_log_customizer_changes($manager) { $log = fopen(ABSPATH . 'customizer_changes.log', 'a'); fwrite($log, date('Y-m-d H:i:s') . " - Customizer changes saved.n"); fclose($log); } add_action( 'customize_save_after', 'weplugins_log_customizer_changes', 10, 1 );
Example 3: Sending Notification Emails
This example sends an email notification whenever the customizer settings are saved.
function weplugins_notify_admin_on_customizer_save($manager) { wp_mail('admin@example.com', 'Customizer Settings Saved', 'The customizer settings have been saved.'); } add_action( 'customize_save_after', 'weplugins_notify_admin_on_customizer_save', 10, 1 );
To remove a hook callback, use the example below.
remove_action( "customize_save_after", "weplugins_execute_on_customize_save_after_event", 10, 1 );
Please make sure to provide the same callback function name, priority, and number of arguments while removing the hook callback.
Contact Us
If you’re having any trouble using this hook, please contact our WordPress Development Team and we’d be happy to assist you.
Explore the latest in WordPress
Trying to stay on top of it all? Get the best tools, resources and inspiration sent to your inbox every Wednesday.