Skip to content

Release 1.12.0: PHP error monitoring - #66

Merged
barrykooij merged 8 commits into
mainfrom
dev
Nov 14, 2026
Merged

barrykooij merged 8 commits into
mainfrom
dev

Conversation

@barrykooij

@barrykooij barrykooij commented Nov 14, 2026 •

Copy link
Copy Markdown
Member

PHP error monitoring, the plugin side.

  • PHP errors: fatal errors and warnings are caught, grouped by fingerprint and counted, credited to the plugin, theme or WordPress core that raised them, and sent to Scanfully. New errors go within a minute, counts hourly, and a new fatal error right away.
  • Must-use plugin: to catch errors raised while other plugins load, the plugin adds its must-use plugin, scanfully-mu.php, to wp-content/mu-plugins when that folder is writable. It removes the file when the plugin is deactivated, disconnected or deleted. Without it, errors raised after plugins load are still caught (coverage "partial").
  • One must-use plugin for anything early: the file is a general loader. It only includes src/mu.php from the plugin, which decides what starts before other plugins load (today the PHP error monitor), so a later feature that needs to run early changes the plugin, not the file on the site.
  • Privacy: email addresses, passwords, keys, tokens and query strings are removed from messages; traces have no function arguments; file paths are relative to the WordPress folder. The readme lists the data under External services.
  • Always on while the site is connected, as part of Scanfully's monitoring; there is no setting to turn it off.
  • Version: 1.12.0, with its changelog in the readme.

Needs Scanfully API v2.7.0 or newer, which is live.

  • Merge with a merge commit, then publish release 1.12.0, which puts it on wordpress.org.
  • If the release is not on 14 November 2026, change the date in the readme changelog first.

Tested

  • composer qa: lint and PHPStan clean, 741 unit tests pass.
  • Integration suite in wp-env, legacy and HPOS order storage: 219 tests pass in each (one skipped: the read-only folder test cannot run as root). It covers a fatal error while a plugin loads being caught by the must-use plugin and sent, and errors after plugins load being caught without it.
  • Deactivating, activating again and deleting the plugin: scanfully-mu.php is removed on deactivate and on uninstall, written again on activate, and a file of that name that isn't Scanfully's is left alone.
  • On two live sites: both report full coverage with scanfully-mu.php installed, stay connected and keep reporting. A test warning was caught, credited to the file that raised it, and shown in Scanfully with the query string removed from the URL path.
  • Not tested: multisite and translated sites.

…m before other plugins load, grouped and counted, credited to the plugin, theme or WordPress core that raised them, and sent to Scanfully with emails, keys, passwords and query strings removed
…ust-use plugin it adds, under External services
…aught by the must-use plugin and sent, and that without it the plugin still catches errors raised after plugins load
…arnings, counts that grow while errors are sent keep their sample, and long file paths in PHP error messages are no longer removed as keys
…ything Scanfully starts before other plugins load
…off, so it always runs while the site is connected
@barrykooij
barrykooij merged commit eee6782 into main Nov 14, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant