| 1 |
<?php |
| 2 |
|
| 3 |
/** |
| 4 |
* Fired when the plugin is uninstalled. |
| 5 |
* |
| 6 |
* When populating this file, consider the following flow |
| 7 |
* of control: |
| 8 |
* |
| 9 |
* - This method should be static |
| 10 |
* - Check if the $_REQUEST content actually is the plugin name |
| 11 |
* - Run an admin referrer check to make sure it goes through authentication |
| 12 |
* - Verify the output of $_GET makes sense |
| 13 |
* - Repeat with other user roles. Best directly by using the links/query string parameters. |
| 14 |
* - Repeat things for multisite. Once for a single site in the network, once sitewide. |
| 15 |
* |
| 16 |
* This file may be updated more in future version of the Boilerplate; however, this is the |
| 17 |
* general skeleton and outline for how the file should work. |
| 18 |
* |
| 19 |
* For more information, see the following discussion: |
| 20 |
* https://github.com/tommcfarlin/WordPress-Plugin-Boilerplate/pull/123#issuecomment-28541913 |
| 21 |
* |
| 22 |
* @link http://mlsimport.com/ |
| 23 |
* @since 1.0.0 |
| 24 |
* |
| 25 |
* @package Mlsimport |
| 26 |
*/ |
| 27 |
|
| 28 |
// If uninstall not called from WordPress, then exit. |
| 29 |
// Guard: WordPress only defines WP_UNINSTALL_PLUGIN when running the uninstall hook, |
| 30 |
// so any direct request to this file bails out here before any code runs. |
| 31 |
if ( ! defined( 'WP_UNINSTALL_PLUGIN' ) ) { |
| 32 |
exit; |
| 33 |
} |
| 34 |
// NOTE: past the guard the file currently performs no cleanup — the boilerplate skeleton |
| 35 |
// only guards its entry point; no options/CPT/meta removal is implemented here. |
| 36 |
|
