Monitoring
PHP errors hide in log files that nobody reads — until a fatal error takes down the site. BlockForge monitors PHP error logs across all your WordPress installations, surfacing fatal errors, deprecation warnings, and plugin conflicts in real time. Fix issues before they escalate.
The Problem
A fatal error in a rarely-visited page can go unnoticed for weeks. The contact form throws a fatal on submission, the WooCommerce checkout crashes for a specific payment gateway, or the admin settings page dies on save. These errors sit silently in log files while users encounter broken functionality and leave without telling you.
Error logs spread across dozens of servers and hosting accounts — nobody has time to SSH into every server and tail every error log manually. Even when you do check, logs are often enormous, mixing critical fatal errors with thousands of harmless deprecation notices. Finding the signal in the noise is nearly impossible at scale.
One plugin throws hundreds of deprecation warnings that flood the log, masking real errors from another plugin. A security plugin conflict with a caching plugin produces intermittent fatals. Without proper error attribution and deduplication, you waste hours investigating noise instead of fixing the actual problems.
How It Works
Uncaught Error: Call to undefined method WC_Cart::get_total()
Maximum execution time of 30 seconds exceeded
Deprecated: Function create_function() is deprecated
Undefined index: user_role in settings handler
BlockForge collects PHP errors from every connected WordPress site and presents them in a single, structured dashboard. Errors are automatically parsed to extract the error type, file path, line number, and stack trace. Duplicate errors are grouped and counted so you see "47 occurrences of this fatal error" instead of 47 individual log lines. Each error is attributed to its source plugin or theme, making it immediately clear which component is causing problems.
Capabilities
PHP errors are collected from each site's error log in near real-time. When a fatal error occurs on any of your managed sites, it appears in your dashboard within minutes — no need to SSH into servers, no cron delays, no manual log checking. Errors are parsed and structured as they arrive.
Errors are categorized by severity level — Fatal, Warning, Notice, and Deprecated. Filter your view to show only the errors that matter right now. Focus on fatal errors during incident response, review deprecation warnings during maintenance windows, and suppress known notices until you're ready to address them.
Error occurrence rates are tracked over time to identify escalating problems. A warning that appeared 5 times yesterday but 50 times today signals a developing issue. Trend alerts notify you when error rates spike, helping you catch problems during the warning phase before they become full-blown outages.
Every error is automatically attributed to its source — plugin, theme, or WordPress core. File paths in error messages are parsed and matched against installed components. You see at a glance that "woo-addon" is responsible for 47 fatal errors and "legacy-forms" generates 203 deprecation warnings.
Toggle WP_DEBUG and WP_DEBUG_LOG remotely from the BlockForge dashboard — no SSH access, no file editing, no FTP required. Enable debug mode when investigating an issue, collect detailed error output, then disable it when done. All without touching the production wp-config.php manually.
Identical errors are automatically grouped and deduplicated. Instead of scrolling through thousands of individual log lines, you see unique error patterns with occurrence counts, first-seen and last-seen timestamps, and affected sites. One view, zero noise, full clarity across your entire portfolio.
Start monitoring PHP errors across all your WordPress sites. Real-time collection, severity filtering, and plugin attribution included. Free plan includes 3 sites.