I haven’t tested this, so it might not work correctly, but the essence of what you’re trying to do is hook into the after_switch_theme hook and see if the $old_name is DahTheme. If it is, that means that the current theme isn’t DahTheme, so you want to deactivate the plugin. function wpse_after_switch_theme( $old_name, $old_theme ) … Read more
Method 1 You can use activate_plugin() and deactivate_plugins() to activate/deactivate plugins programmatically. If you want to control the time at which those actions happen, then you can use wp_schedule_event() too. Method 2 I know you asked about PHP, but if you have WP-CLI installed on your server, you can also write a script that uses … Read more
There’s two ways to do this, you can either check for the main plugin file or you can check for the WooCommerce class. When I make a plugin dependent on some other plugin I usually check for the plugin file, but for WooCommerce I check for the WooCommerce class. <?php function yourplugin_init() { if( !function_exists( … Read more
As far as I know, a plugin can be deactivated in these conditions: manual deactivation failed plugin upgrade remove or rename the containing folder changing the active plugin list in the database Hopefully someone else will come through and add to this if I missed any.
You shouldn’t cleanup the database on the deactivation hook. As @Darhazer said, use the uninstall hook or create an uninstall.php inside the plugin folder. What you can do is to create an export settings page, which the user can use to save/backup his data. You could call this page before deativation, so the user will … Read more
I have implemented a workaround with JavaScript. I’m loading my own JavaScript file: wp_enqueue_script(‘wp-deactivation-message’, plugins_url(‘js/message.js’, dirname(__FILE__)), array()); which contains a script that adds following Event Listener – when user clicks on our plugin deactivate button it prevent it from performing this action and display a JavaScript popup asking what you need, if user accepts it … Read more
Yes, register a deactivation hook in your first plugin, and inside this hook deactivate the 2nd plugin using the deactivate_plugins() function
Here’s my bare-bones template that I use when creating a plugin with OOP. Feel free to modify to your liking. Template if ( !defined( ‘ABSPATH’ ) ) exit; // Exit if accessed directly if ( !class_exists( ‘MyPluginName’ ) ) { class MyPluginName { public function __construct() { // Call your actions/filters here add_action( ‘tag’, array( … Read more
Actually, there’s a better way. All of my plugins require PHP5. Until recently, that wasn’t a requirement in WordPress, so a lot of people tried to install my plugins on systems missing vital PHP functions. I added some checks to my plugin to make sure it would work and, if not, display a message. But … Read more
What @Sumit says in the comments (and you found out for yourself) is correct. If you deactivate a plugin in a theme it is deactivated permanently, until it is activated again. Also, if you attach your deactivation action to wp_head it is executed at every pageload, which is not necessary. What you need to do … Read more