Upgrade Readiness Monitor
| 开发者 | dhanendran |
|---|---|
| 更新时间 | 2026年6月18日 12:03 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Real-time deprecation capture. The plugin listens for WordPress's deprecation signals (
deprecated_function_run,deprecated_hook_run,doing_it_wrong_run, and friends) as your site runs. Because those signals fire regardless ofWP_DEBUG, you catch real deprecations on production without turning on debug mode — each one attributed to the plugin or theme that triggered it. - Plugin & theme audit. A one-click scan checks every installed plugin and your active theme against WordPress.org for abandoned code (no update in 2+ years), "tested up to" lag, available updates, and declared PHP requirements.
- Static code scan against your chosen target. Every plugin and theme — including custom and premium code that isn't on WordPress.org — has its PHP parsed and checked against the WordPress and PHP versions you plan to upgrade to. Findings are graded Error (will break — e.g. a function removed in the target PHP version) or Warning (a deprecation notice you'll start seeing). The functions the target WordPress version deprecates are read from WordPress core itself, so results reflect the actual upgrade.
- No configuration — install, choose your target, and scan.
- Read-only and safe: it never changes your site.
- The audit runs in the background in small chunks, so it never blocks or slows a page load.
- WP-CLI included:
wp readiness checkprints the full report and exits non-zero on a red verdict, so you can gate upgrades in CI/staging.
安装:
- Upload the
upgrade-readiness-monitorfolder to/wp-content/plugins/, or install it from the Plugins screen. - Activate the plugin.
- Go to Tools → Upgrade Readiness, choose your target WordPress/PHP versions, and click Scan now.
常见问题:
Does it change anything on my site?
No. It only reads and reports. Deprecation notices are captured passively and stored locally; the audit reads plugin/theme headers, public WordPress.org data, and your plugins'/theme's own PHP files.
Do I need WP_DEBUG on?
No. WordPress fires its deprecation hooks whether or not WP_DEBUG is enabled, so the monitor works on production.
How accurate are the Error / Warning findings?
"Error" findings are conservative and high-confidence: they come from a hand-verified list of PHP functions genuinely removed in the target PHP version (calling them is a fatal error). "Warning" findings are deprecations — code that still works but emits a notice on the target. The WordPress deprecation list for your target version is read from WordPress core itself. The scan is precise rather than exhaustive: it reports problems it is confident about and never invents findings. It does not execute your code, so a clean result is not an absolute guarantee — always do a final test on staging — but a red verdict means there is real, specific breakage to fix first.
What if the target version data can't be fetched?
If WordPress.org can't be reached, the target-version deprecation check is simply skipped (you still get the PHP checks, metadata signals, and runtime capture). The plugin never fabricates results from missing data.
更新日志:
- [Fix] Renamed the main class to the D9URM prefix for full Plugin Check naming compliance; no functional change.
- [Fix] Renamed the WP-CLI class to use the plugin prefix (Plugin Check naming compliance); no functional change.
- [Fix] Scans could appear stuck at "0%" where WP-Cron doesn't fire promptly (low-traffic or local environments). The scan is now driven forward by the report page in bounded chunks, so it always progresses while the page is open; WP-Cron remains the unattended/weekly fallback.
- [Feature] Code is scanned against the version you're upgrading to, with findings graded Error (will break) vs Warning (deprecation). The static scan now runs for all plugins and themes.
- [Feature] WordPress and PHP target selectors — choose the version you're upgrading to. Defaults to the latest available WordPress version.
- [Feature] Local code scan for custom/premium plugins and themes. Live-refreshing deprecation list.
- [Feature] Theme auditing and a Type column. Reload-safe background scanning.
- [Fix] Memory and performance hardening: background processing, minimal API payloads, bounded deprecation capture.
- Initial release: real-time deprecation capture, plugin/theme compatibility audit, readiness verdict, and a
wp readiness checkWP-CLI command.