Download the PHP package error-explorer/wordpress-error-reporter without Composer
On this page you can find all versions of the php package error-explorer/wordpress-error-reporter. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download error-explorer/wordpress-error-reporter
More information about error-explorer/wordpress-error-reporter
Files in error-explorer/wordpress-error-reporter
Package wordpress-error-reporter
Short Description Error reporting plugin for WordPress applications - automatically sends errors to Error Explorer monitoring platform
License MIT
Informations about the package wordpress-error-reporter
Error Explorer WordPress SDK
Automatically send WordPress errors to Error Explorer monitoring platform for better error tracking and debugging.
Features
- 🚨 Automatic error detection and reporting
- 📊 Detailed error context (request, session, server data)
- 🔍 Stack traces and breadcrumbs
- ⚙️ Easy WordPress admin configuration
- 🔒 Sensitive data sanitization
- 🎯 WordPress-specific error handling
- 📱 Supports WordPress multisite
- 🔧 Test error functionality
Installation
Method 1: WordPress Plugin (Recommended)
- Download the plugin files to your WordPress
wp-content/plugins/
directory - Activate the plugin through the WordPress admin
- Configure the plugin in Settings > Error Explorer
Method 2: Composer Installation
Then include in your WordPress theme or plugin:
Configuration
WordPress Plugin Configuration
- Go to Settings > Error Explorer in your WordPress admin
- Configure the following options:
Option | Description | Default |
---|---|---|
Enable Error Reporting | Enable/disable error reporting | Disabled |
Webhook URL | Your Error Explorer project webhook URL | Empty |
Capture Request Data | Include request data (GET, POST, headers) | Enabled |
Capture Session Data | Include session and user data | Enabled |
Capture Server Data | Include server environment data | Enabled |
Getting Your Webhook URL
- Log in to your Error Explorer dashboard
- Go to your project settings
- Copy the webhook URL (format:
https://your-domain.com/webhook/error/your-token
)
Manual Configuration
Usage
Automatic Error Handling
Once configured, the SDK automatically captures:
- PHP Fatal Errors
- PHP Warnings and Notices
- Uncaught Exceptions
- WordPress
wp_die()
calls - Plugin and theme errors
Manual Error Reporting
Breadcrumbs for Better Context
Add breadcrumbs to track user actions before an error:
WordPress Integration Examples
Theme Integration
Add to your theme's functions.php
:
Plugin Integration
WooCommerce Integration
Track WooCommerce-specific events:
Testing
Test Error Functionality
The plugin includes a test error feature accessible from the admin settings page, or you can trigger it manually:
Using the Test Project
A complete test project is available in test-wordpress-project/
:
This will run various error scenarios to test the SDK functionality.
Captured Data
The SDK captures comprehensive error context:
Error Information
- Exception message and class
- Stack trace
- File and line number
- Error fingerprint for grouping
Request Data (if enabled)
- URL, method, IP address
- GET/POST parameters (sanitized)
- HTTP headers (sanitized)
- User agent and referer
WordPress Data
- WordPress version
- Current theme and plugins
- User information (if logged in)
- Multisite information
- Debug settings
Server Data (if enabled)
- PHP version and memory usage
- Server software and environment
- Memory limits and execution time
- Document root and server name
Session Data (if enabled)
- Session ID and name
- Current user details
- User roles and capabilities
Security
The SDK automatically sanitizes sensitive data:
- Passwords and tokens are redacted
- Authorization headers are masked
- Sensitive form fields are filtered
- API keys and secrets are protected
Troubleshooting
Common Issues
-
Errors not appearing in dashboard
- Check webhook URL is correct
- Verify error reporting is enabled
- Check WordPress error logs for SDK errors
-
Permission errors
- Ensure WordPress has permission to make HTTP requests
- Check firewall rules for outbound connections
- Missing dependencies
- Run
composer install
if using Composer - Ensure Guzzle HTTP client is available
- Run
Debug Mode
Enable WordPress debug mode to see SDK errors:
Check /wp-content/debug.log
for SDK-related messages.
Requirements
- PHP 7.4 or higher
- WordPress 5.0 or higher
- Guzzle HTTP client
- cURL extension
Support
For support and documentation, visit Error Explorer Documentation or create an issue in the project repository.
License
MIT License - see LICENSE file for details.