| 开发者 | nicognito23 |
|---|---|
| 更新时间 | 2026年10月13日 11:11 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
Update URI), must-use plugins and drop-ins are not tracked and never show a warning.
Enable, recheck, stop
After activation, a notice on the Plugins screen (only there) explains what will be sent and offers an Enable checks button. Each user can dismiss it; Enable checks stays available from the plugin's row. The notice never appears elsewhere in the admin and disappears for good once checks are enabled. Once enabled, the plugin's row offers:
/wp-content/plugins/ or install it from the Plugins screen.The plugin waits for your consent: click Enable checks in the notice on the Plugins screen. Checks then run in the background through WP-Cron, a few plugins at a time. On a site with many plugins, the first full check can take several minutes.
Checks only run when WP-Cron runs. If DISABLE_WP_CRON is set, make sure a real system cron calls wp-cron.php (or runs wp cron event run --due-now) regularly, otherwise results will not be refreshed and "Recheck now" will wait for the next cron run.
Only plugins hosted on WordPress.org can be tracked. When the plugin cannot be confirmed as the WordPress.org one (for example a custom plugin whose folder name matches a WordPress.org slug but whose name differs), it is deliberately left untracked to avoid a false alert.
Users who can activate plugins (activate_plugins).
Multisite is not officially supported in version 1.0 and has not been tested. Use it on single-site installations.
Deactivation and "Stop checks" remove the stored results, the consent setting, the lock transient and all scheduled events; after reactivation, checks must be enabled again. Uninstall removes the same data plus each user's "notice dismissed" setting.