mirror of
https://github.com/inretio/WordPress-Plugin-Boilerplate
synced 2024-04-27 17:03:15 +03:00
5391e0ca27
Flattening the folder structure for a bit easier auto-inclusion into projects and local development. See: https://github.com/DevinVinson/WordPress-Plugin-Boilerplate/issues/295
32 lines
1 KiB
PHP
32 lines
1 KiB
PHP
<?php
|
|
|
|
/**
|
|
* Fired when the plugin is uninstalled.
|
|
*
|
|
* When populating this file, consider the following flow
|
|
* of control:
|
|
*
|
|
* - This method should be static
|
|
* - Check if the $_REQUEST content actually is the plugin name
|
|
* - Run an admin referrer check to make sure it goes through authentication
|
|
* - Verify the output of $_GET makes sense
|
|
* - Repeat with other user roles. Best directly by using the links/query string parameters.
|
|
* - Repeat things for multisite. Once for a single site in the network, once sitewide.
|
|
*
|
|
* This file may be updated more in future version of the Boilerplate; however, this is the
|
|
* general skeleton and outline for how the file should work.
|
|
*
|
|
* For more information, see the following discussion:
|
|
* https://github.com/tommcfarlin/WordPress-Plugin-Boilerplate/pull/123#issuecomment-28541913
|
|
*
|
|
* @link http://example.com
|
|
* @since 1.0.0
|
|
*
|
|
* @package Plugin_Name
|
|
*/
|
|
|
|
// If uninstall not called from WordPress, then exit.
|
|
if ( ! defined( 'WP_UNINSTALL_PLUGIN' ) ) {
|
|
exit;
|
|
}
|