How to use pre_current_active_plugins action in WordPress

pre_current_active_plugins action

This hook also fires before the plugins list table is rendered in the Network Admin.

To use pre_current_active_plugins action, first you have to register it using add_action. You can write this code into functions.php of your activated theme or in a custom WordPress Plugin.

We at WePlugins always prefer to create a custom WordPress Plugin while using hooks so nothing breaks when you update your WordPress Theme in the future.

In the below live example, we have defined a function weplugins_execute_on_pre_current_active_plugins_event which takes 1 parameter and we registered using add_action. The first parameter pre_current_active_plugins is the name of the hook, The second parameter weplugins_execute_on_pre_current_active_plugins_event is the name of the function which 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 pre_current_active_plugins action.

Parameters

Below is the 1 parameter required to use this hook.

• $plugins_all : (array[]) An array of arrays containing information on all installed plugins.

Live Example

Example 1: Basic Execution

Below is an example of how you can use this hook.

    function weplugins_execute_on_pre_current_active_plugins_event($plugins_all){
        // You can write code here to be executed when this action occurs in WordPress.
        // Use the parameters received in the function arguments & implement the required additional custom functionality according to your website requirements.
    }
    // add the action
    add_action("pre_current_active_plugins", "weplugins_execute_on_pre_current_active_plugins_event", 10, 1);
    

Example 2: Removing the Hook

To remove a hook callback, use the example below.

    remove_action("pre_current_active_plugins", "weplugins_execute_on_pre_current_active_plugins_event", 10, 1);
    

Example 3: Custom Functionality

In this example, we are logging the active plugins to a custom log file.

    function weplugins_log_active_plugins($plugins_all){
        $log = fopen("path_to_log_file.log", "a");
        fwrite($log, print_r($plugins_all, true));
        fclose($log);
    }
    // add the action
    add_action("pre_current_active_plugins", "weplugins_log_active_plugins", 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 need customization or are having any trouble using this hook, please contact us and we’d be happy to assist you.