This section covers advanced functionality for power users and developers.

Custom Log Path Support

The plugin automatically detects custom log file paths defined in your WordPress configuration. This supports non-standard locations for debug.log files, which is useful when you need to store logs outside the default WordPress directory structure.

Plugin Auto-Detection Methods

The plugin scans common WordPress directories and checks for alternative debug log locations. It uses multiple detection methods to locate your debug.log file, including:

• Standard WordPress root directory
• wp-content directory
• Custom paths defined in wp-config.php

Limitations with Custom Paths

Some features may be limited if the custom path is outside standard directories. Ensure that the custom path is writable by WordPress to avoid access issues.

Debug Constants Behavior with Custom Paths

WP_DEBUG_LOG must still be defined in wp-config.php, even when using custom paths. The plugin adapts to the specified path while maintaining all core functionality.

Export Features (Pro)

The Pro version provides CSV export capabilities with advanced filtering options. This allows you to download logs for external analysis.

Exporting Logs to CSV Format

Download logs as comma-separated values compatible with spreadsheet software. This format is ideal for:

• Importing into Excel or Google Sheets
• Creating visualizations and charts
• Sharing with team members

Date Range Filtering for Exports

Select specific time periods for export to focus on relevant data. This feature is particularly useful when:

• Investigating issues during specific time windows
• Generating reports for particular periods
• Analyzing trends over time

Custom Time Range Selection

Set start and end dates for export using the date picker interface. You can filter by:

• Specific hours within a day
• Full days or weeks
• Custom date ranges

Using Exported Data for Analysis

Import exported CSV files into your preferred analysis tools. This allows you to:

• Apply advanced filtering and sorting
• Create pivot tables for trend analysis
• Generate charts and graphs

CSV Structure and Columns

Exported files include all log table columns:

• Timestamp: When the error occurred
• Type: Error level (Notice, Warning, etc.)
• Description: Detailed error message
• File: Source file path
• Line: Line number in the file
• Stack Trace: Full call hierarchy

The log file Security

The plugin includes features to help you secure your debug log files.

Debug File Accessibility Warnings

The plugin detects if your log file is publicly accessible and alerts you to potential security risks. This helps prevent sensitive information from being exposed.

The plugin verifies whether debug.log can be accessed via browser. It checks direct URL access to the file

Security Best Practices

Follow these recommendations to secure your debug logs:

• Place debug.log outside the web root when possible
• Restrict file permissions to 640 or more restrictive
• Regularly clean up old logs

.htaccess Protection Recommendations

Add these rules to your .htaccess file:

<Files ~ "^debug\.log$">
  Order deny,allow
  Deny from all
</Files>

This prevents public access while maintaining plugin functionality.

This guide provides practical examples for different user types.

For Developers

Debugging Plugin Conflicts

Enable WP_DEBUG and WP_DEBUG_LOG to start capturing errors. Reproduce the conflict scenario and check logs for Fatal Errors or Database Errors.

Tracking Deprecation Warnings

Filter logs by “Deprecated” error type to identify outdated functions. Use SearchBuilder to find specific deprecated calls in your codebase.

Monitoring Database Query Errors

Filter by “Database Error” type to check for slow queries or connection issues. Optimize problematic database operations based on the error details.

Identifying Performance Bottlenecks

Look for repeated Warning entries and check stack traces for time-consuming functions. Use the datetime filter to correlate with slow page loads.

Using Stack Traces Effectively

Click on a log entry to expand the stack trace. Follow the call hierarchy from bottom (origin) to top (error). Identify which function or plugin triggered the issue.

For Site Administrators

Monitoring Site Health

Set up daily alerts for Fatal Errors and Database Errors. Review logs weekly for recurring issues. Use the relative time format to spot recent problems.

Identifying Problematic Plugins/Themes

Filter logs by file path to find plugin-specific errors. Check for errors originating from /wp-content/plugins/. Deactivate suspicious plugins and monitor for improvements.

Setting Up Preventive Maintenance Alerts

Configure alerts for Warning or Fatal-level errors. Set frequency to “Twice Daily” for active monitoring. Add your maintenance team’s email addresses.

Regular Log File Cleanup

Schedule automatic cleanup to run daily. Set maximum log size to 5MB for optimal performance. Keep the last 10% of logs for historical reference.

Security Monitoring

Filter logs by “Parse Error” to catch syntax issues. Monitor for unusual file access patterns. Set up alerts for errors in security-sensitive plugins.

For Agencies

Managing Multiple Client Sites

Use the same alert configuration across all client sites. Standardize error level monitoring (Fatal + Database Errors). Document each site’s typical error patterns.

Standardized Monitoring Setup

Create a checklist for new client onboarding:

• Enable debug logging
• Configure alerts with agency email
• Set cleanup schedule

Client Site Email Alerts Configuration

Add client contact emails as recipients (Pro). Set appropriate alert frequency based on site activity. Document alert configurations for each client.

Automated Log Maintenance Strategies

Implement cleanup schedules based on site traffic:

• High-traffic: Every 6 hours
• Medium-traffic: Twice daily
• Low-traffic: Daily

Reporting and Documentation

Export logs monthly for client reports (Pro). Use CSV exports to create error trend charts. Document recurring issues and resolutions.

For technical reference, see the Technical Reference guide.