It was actually much easier than I originally thought – just doing a WP_User_Query for a meta value (meta arrays are supported as well, like for the other query classes). public function on_deactivate() { $meta_key = ‘tools_page_tsi_per_page’; $query = new WP_User_Query( array( ‘meta_key’ => $meta_key ) ); if ( empty( $query->results ) ) return; foreach … Read more
You should prefer the uninstall hook over the file if your main plugin doesn’t have side effects (outputs html or writes to file/DB automatically when loaded). IMO there is too much risk (i.e. non zero) of doing the uninstall.php code wrong and open the file to direct execution from the outside. This also help in … Read more
You can’t. WordPress tracks the recently active plugins for a while, but there is no history of deleted plugins. You could install a logger and track this information in a special place for the future.
Something along these lines: Create a new WordPress install in the place you want your install to be Put it in maintenance mode migrate the content Log in and adjust options accordingly To migrate the content you have two choices: 1 – Copy the data from the tables of the blog/site that you want to … Read more
You just need to obtain the basename of any plugin to deactivate it. if( $uninstall == true ) { delete_option( ‘CHANGETHIS’ ); deactivate_plugins( plugin_basename( __FILE__ ) ); } Generally they look like mypluginfolder/mypluginmasterfile.php Give that a shot. There are a variety of ways to getting it to work. If you want a button on the … Read more
All of my theme’s custom options are preceeded with “mytheme_” + option. Not safe enough. Use set_theme_mod(), get_theme_mod() and remove_theme_mod() instead. You’ll find these and more related functions in wp-includes/theme.php.
Because it is a wiki, the codex is a notoriously unreliable source of information (but you probably already knew that). However, it is probably true that uninstalling on huge networks will not scale. What I do in one of my plugins is run the plugin’s uninstall routine on all sites, unless wp_is_large_network() is true. On … Read more
Sure, just call the delete_plugins() function, found in wp-admin/includes/plugin.php – you have to manually require() it.
This is indeed bizarre. I think they first tried it with dbDelta, found it doesn’t work with DROP queries, and went with a straight $wpdb query instead. They then just forgot to take out the dbDelta stuff. It appears dbDelta collects creation queries in $cqueries and insert queries in $iqueries, but silently ignores the rest. … Read more
I don’t think that you should touch these options. WordPress core already handles this, whether by removing the references to your plugin when it is deleted (as in delete_plugins()), or by being coded in such a way that it can ignore the reference to the removed plugin. Actually, none of these three options will last … Read more