Linux 软件免费装
Banner图

The Hack Repair Guy's PHP Checker

开发者 hackrepair
tvcnet
更新时间 2026年11月22日 04:57
捐献地址: 去捐款
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

php compatibility upgrade php 8.4 php 8.3

下载

1.2.5 1.2.8

详情介绍:

Upgrading PHP is one of the best ways to keep WordPress fast and secure, right up until an older plugin throws a fatal error on upgrade day. PHP Checker helps you find that plugin before you switch. The Hack Repair Guy's PHP Checker runs entirely inside WordPress (no exec() or shell access needed), automatically filters out runtime version guards and polyfills, and prioritizes potential fatal errors and unknown-impact findings for review. Open Tools > PHP Checker, pick your target PHP version (8.1, 8.2, 8.3, 8.4, or 8.5), and click Scan. It checks: Designed for first-time users and seasoned developers alike. A plain-English readiness banner at the top of the report helps you identify findings that need review before upgrading. Fatal incompatibilities sit at the very top with their file:line error tables open; minor deprecation warnings are grouped below with collapsible technical drawers so you are never overwhelmed by a wall of stack traces. Your scans build a local history. Completed scans are saved on your own site (up to 25 reports within a 600,000-byte limit), showing what is new and what you have fixed since your previous check for that PHP version. Pause, reopen, delete, or clear history anytime. Share or email a report. Copy the plain-text report for a developer or support ticket, download a .txt file, print a clean summary, or email a formatted HTML and plain-text PHP readiness briefing to site administrators with [domain] [PHP Checker] subject tags. Optional scheduled PHP readiness email. Off by default. Choose weekly (with a day of the week) or monthly (day 1 to 28) to automatically email site administrators a PHP readiness report, or only when errors or warnings are found. Privacy Static scans inspect local PHP source files on your server in 5-second AJAX steps without executing plugin/theme code or sending source code or report contents to any outside service. Optional Update Pre-Scan (off by default) downloads pending update zip packages from their configured update URLs to a temporary file, inspects PHP entries in memory, and deletes the temporary file immediately. Scan results and report history stay in your site's database and automatically prune uninstalled plugins/themes. Reports leave your site only when an administrator copies, downloads, prints, or emails them, or enables the monthly email. See External services below for the few requests PHP Checker makes, and when. What it is not Static analysis parses PHP source tokens without executing your site's code. While version-guard handling downgrades common backward-compatibility code to notes, static analysis cannot replace testing critical workflows (like WooCommerce checkout or membership forms) on a staging server before switching PHP versions in production. If you want a deeper look or hands-on help with a tricky PHP upgrade, The Hack Repair Guy can help. Credits Static analysis uses PHP_CodeSniffer 4.0.4 (BSD-3-Clause), PHPCSUtils 1.2.3 (LGPL-3.0-or-later), PHPCompatibility (development snapshot, commit a0fd248812fd, LGPL-3.0-or-later), PHPCompatibilityWP 3.0.0-alpha2 (LGPL-3.0-or-later) and PHPCompatibilityParagonie 2.0.0-alpha2 (LGPL-3.0-or-later). They are bundled in vendor/thrg-scan-engine/ as runtime code, loaded only when an administrator runs a scan; unused tools and tests are removed and each folder keeps its license.

安装:

  1. In WordPress, open Plugins > Add New, search for "The Hack Repair Guy's PHP Checker" and choose Install Now. You can also upload the thrg-php-checker folder to wp-content/plugins/.
  2. Activate The Hack Repair Guy's PHP Checker.
  3. Open Tools > PHP Checker, select your target PHP version (PHP 8.3 is selected by default), and click Scan.
  4. Review the plain-English Readiness Verdict banner at the top and the "Compatibility errors" findings first.
  5. Optional: open Share, Download, Print, or Email This Report to send a copy to your developer or other administrators, or set up the Scheduled Readiness Email.

屏幕截图:

  • Export, scheduled monitoring, runtime deprecation log, saved reports and scanner settings.
  • Start screen: choose a PHP target version and scan scope.

常见问题:

What is the difference between an Incompatible error and a Deprecation warning?

  • Incompatible (Fatal Error — Red): The plugin or theme uses a function, class, or syntax that was removed or fatally changed in the target PHP version (without a runtime version guard). If that code path runs on the target PHP version, PHP will halt the request with a fatal error. Update, replace, or deactivate red items before upgrading PHP.
  • Deprecation Warning (Amber): The plugin or theme uses a feature that still works in the target PHP version, but PHP logs an E_DEPRECATED notice to let developers know it will be removed in a future PHP version. Your site can still run on the target PHP version today (keep WP_DEBUG_DISPLAY off on live production sites and update the plugin as new releases arrive).

How does PHP Checker handle version guards and polyfills?

Many WordPress plugins support both older and newer PHP versions by wrapping legacy calls in version_compare( PHP_VERSION, '8.0', '<' ) or if ( ! function_exists( 'str_contains' ) ) polyfills. Those lines never run on newer PHP versions, so they are not real problems. PHP Checker's token-stream analyzer (THRG_PC_Context) inspects surrounding if/elseif/else conditions and early-return guards, automatically downgrading safe fallbacks to collapsed informational notes.

How does the PHP 8.2+ dynamic property check avoid noisy false alarms?

PHP 8.2 deprecated creating undeclared properties on class instances, with official exceptions documented in the PHP 8.2 Migration Guide. PHP Checker inspects class declarations and inheritance chains in each file and skips classes with #[AllowDynamicProperties] (direct or inherited), stdClass and its subclasses, classes implementing magic __set(), constructor-promoted properties, and declared properties.

What do the "Plugin code" and "Bundled dependency" badges mean?

Every file:line finding shows whether the file lives in the plugin/theme's own code (Plugin code / Theme code) or inside a bundled third-party library (Bundled dependency, such as vendor/, freemius/, action-scheduler/, pear/, or phpmailer/). This helps developers and site owners know immediately whether an issue is in custom code they control or an upstream SDK that will be updated by the vendor.

Does scanning slow down visitors or time out on large plugins?

No. Scanning runs only when an administrator starts it (or turns on the scheduled readiness email) and processes files in 5-second time-boxed AJAX slices. If a single large plugin has thousands of files, PHP Checker saves file-level progress after 5 seconds and resumes on the next slice automatically. Files larger than 2 MB are skipped safely and marked as partial rather than crashing PHP memory.

What happens when I uninstall or delete a plugin that had errors?

PHP Checker automatically prunes uninstalled plugins/themes and outdated component versions whenever results are loaded. Uninstalling PHP Checker itself removes all of its options and scheduled hooks cleanly.

更新日志:

1.2.8 1.2.7 1.2.6 1.2.5 1.2.4 1.2.3 1.2.2 1.2.1 1.2.0 1.1.0 1.0.0