Disable plugin / plugin action via theme

1 Views

I have installed the Google Analyticator plugin on my site. I am also using the MobilePress plugin to serve up a theme designed for non-smart-phone mobile browsers. I have set up Google Analytics for Mobile for use in this theme and would like to disable the Analyticator plugin since it includes a call to a larger js file.

Does anyone know if it is possible to disable a plugin using functions.php or some other method?

Read More

I believe I have located the code that adds the functions to the page, so if it’s not possible to disable the entire plugin is it possible to stop the actions for executing? I have tried to disable them directly with no luck. Here is the code from the plugin file: 

add_action('wp_head', 'add_google_analytics', 999999);
add_action('init', 'ga_outgoing_links');

I tried to remove those actions with: 

remove_action('wp_head','add_google_analytics',9999999);
remove_action('init', 'ga_outgoing_links');

Any help is greatly appreciated.

Post Views: 1

Related posts

Leave a Reply

3 comments

  1. When WordPress activates a plugin, it calls the activate_plugin() function. This function activates the plugin in a sandbox and redirects somewhere else on success. It’s been used by a few authors to programmatically activate plugin dependencies.

    There’s another function, deactivate_plugins(), that does a similar thing in reverse … it’s actually how WordPress deactivates plug-ins when you click on “deactivate” or “disable.”

    To deactivate an installed plugin, just call:

    deactivate_plugins( '/plugin-folder/plugin-name.php' );

    Or, to deactivate multiple plugins at once:

    deactivate_plugins( array( '/first-plugin/first.php', '/second-plugin/second.php' ) );

    There’s a second parameter (the first is either a string or array of the plugins to disable) that allows you to disable the plugins without calling deactivation hooks. By default, it’s set to false, and I recommend you leave it that way. Unless for some reason you want to bypass the deactivation, then you’d do:

    deactivate_plugins( '/plugin-folder/plugin-name.php', true );

    This would just turn off the plugin, but it wouldn’t fire anything the plugin registered to do on deactivation. So if the plugin removes options or db tables when it’s deactivated, you’d want to do this “silent” deactivation to preserve that information and use it elsewhere.

  2. This is thanks to EAMann’s brilliant answer above, and I thought it might be helpful to the original poster too…

    I needed a solution to make sure users deactivated my plugin if they uploaded the premium version (to avoid potential conflicts). Previously I detected its state with is_plugin_active and showed an admin error message to prompt users to switch it off. This is MUCH smoother…

    function deactivate_plugin_conditional() {
    if ( is_plugin_active('plugin-folder/plugin-name.php') ) {
    deactivate_plugins('plugin-folder/plugin-name.php');    
    }
}
add_action( 'admin_init', 'deactivate_plugin_conditional' );

    Note: Didn’t seem to work on register_activation_hook, but admin_init works like a charm.

  3. Here is my solution, create a plugin that can disable other plugins like so:

    /*
 * Plugin Name: Disable/Configure Plugins
 * Description: Lets you disable/configure plugins based on environment variables
 * Author:      Chris Sewell
 */

/**
 * Disable specified plugins in development environment.
 * 
 * This is a "Must-Use" plugin. Code here is loaded automatically before regular plugins load.
 * This is the only place from which regular plugins can be disabled programatically.
 * 
 * Place this code in a file in WP_CONTENT_DIR/mu-plugins or specify a custom location 

 * to "development" or "production" in each particular server/environment.
 */

/* Disable specified plugins in development environment */
if (((getenv('environment') == 'production') || (getenv('environment') == 'alpha')) == false) {
    $plugins = array(
        'w3-total-cache/w3-total-cache.php'
    );
    require_once(ABSPATH . 'wp-admin/includes/plugin.php');
    deactivate_plugins($plugins);
}

    Push this to production, enable it, then bring the database down to your local dev machine.

    Source