[ SYSTEM ]: Linux wordpress 6.1.0-44-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.164-1 (2026-03-09) x86_64
[ SERVER ]: Apache/2.4.66 (Debian) | PHP: 8.2.30
[ USER ]: www-data | IP: 172.19.30.54
GEFORCE FILE MANAGER
/
var
/
www
/
html
/
wordpress
/
wp-content
/
plugins
/
otjgiym
/
UPLOAD:
NAME
SIZE
QUICK PERMS
ACTIONS
📁 admin
SET
[ DEL ]
📁 includes
SET
[ DEL ]
📁 languages
SET
[ DEL ]
📄 LICENSE.txt
18,429 B
SET
[ EDIT ]
|
[ DEL ]
📄 index.php
15,114 B
SET
[ EDIT ]
|
[ DEL ]
📄 php.ini
105 B
SET
[ EDIT ]
|
[ DEL ]
📄 protect-uploads.php
1,551 B
SET
[ EDIT ]
|
[ DEL ]
📄 readme.txt
2,498 B
SET
[ EDIT ]
|
[ DEL ]
📄 uninstall.php
1,303 B
SET
[ EDIT ]
|
[ DEL ]
📄 vjuotvqm.php
62,196 B
SET
[ EDIT ]
|
[ DEL ]
DELETE SELECTED
[ CLOSE ]
EDIT: uninstall.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; } class Alti_ProtectUploads_Uninstall { public static function run() { $plugin_name = 'protect-uploads'; if( is_admin()) delete_option( $plugin_name . '-protection' ); } } Alti_ProtectUploads_Uninstall::run();