Linux 软件免费装
Banner图

BugTrace - Debug Log Tool

开发者 nsgawli
更新时间 2026年11月13日 22:58
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv3 or later
版权网址: 版权信息

标签

debug log PHP errors troubleshooting tool wordpress debug database info

下载

1.0.0 1.0.1 1.0.4 1.0.8 1.1.1 1.1.2 1.0.7 1.0.2 1.0.3 1.0.5 1.0.6 1.0.9 1.1.0

详情介绍:

Tired of cumbersome debugging processes? BugTrace - Debug Log Tool streamlines WordPress troubleshooting, providing developers and site administrators with a powerful yet minimalist interface to diagnose and resolve issues swiftly. Stop wasting time with manual wp-config.php edits or FTP access for basic debugging tasks. Quick links: Official Website | Documentation With BugTrace, you can: Whether you're developing a new theme or plugin, troubleshooting a tricky bug on a staging server, or performing routine site health checks, BugTrace - Debug Log Tool provides the critical information you need, efficiently and effectively. Other Plugins By Us

安装:

Using The WordPress Dashboard
  1. Navigate to the 'Add New' in the plugins dashboard
  2. Search for BugTrace - Debug Log Tool
  3. Click 'Install Now'
  4. Activate the plugin on the plugin dashboard
Uploading in WordPress Dashboard
  1. Download debug-log-tool.zip from this page
  2. Navigate to the 'Add New' in the plugins dashboard
  3. Navigate to the 'Upload' area
  4. Select debug-log-tool.zip from your computer
  5. Click 'Install Now'
  6. Activate the plugin in the Plugin dashboard
Using FTP
  1. Download debug-log-tool.zip from this page
  2. Extract the debug-log-tool directory to your computer
  3. Upload the debug-log-tool directory to the /wp-content/plugins/ directory
  4. Activate the plugin in the Plugin dashboard
This plugin is almost plug and play!

屏幕截图:

  • Effortless Debug Settings: Toggle WP_DEBUG & Other Constants Instantly.
  • Securely Inspect wp-config.php Contents via the WordPress Admin.
  • Quick.htaccess File Viewer: Essential for Server Troubleshooting.
  • Comprehensive PHP Information (phpinfo()) at Your Fingertips with BugTrace.
  • WordPress Database Table Insights: Monitor Size and Row Counts.
  • Diagnostic View of Active Browser Cookies (Read-Only).
  • Inspect WordPress Transients: Read-Only List for Effective Debugging.
  • Overview of Scheduled WordPress Cron Jobs within the BugTrace Tool.

常见问题:

What are the AI Help Links (ChatGPT, Gemini, Google)?

This is a powerful new feature designed to accelerate your debugging. Next to each error log, you'll find icons for ChatGPT, Gemini, and Google. Clicking one will open a new tab and automatically search that platform for a solution to that specific error, saving you the time of manually copying, pasting, and searching. It's like having an expert assistant for every error.

Can I download the debug.log file?

Yes, if a debug.log file exists and is writable by WordPress, BugTrace allows you to download it directly from the admin panel with a single click.

Is it safe to use BugTrace on a production website?

Yes, BugTrace can be used on a production site. However, exercise caution when enabling debugging modes (like WP_DEBUG or WP_DEBUG_DISPLAY) in a live environment, as this can sometimes expose sensitive information to visitors if errors occur. It's generally recommended for staging or development, or for brief troubleshooting periods on live sites.

How does BugTrace help if I suspect issues with my .htaccess or wp-config.php files?

BugTrace provides a read-only viewer for your .htaccess and wp-config.php files directly within the WordPress admin dashboard. This allows you to quickly inspect their contents for misconfigurations or unexpected code without needing FTP access or risking accidental direct edits to these critical files.

Can I use BugTrace to monitor WordPress cron jobs?

Yes, BugTrace includes a feature to view your scheduled WordPress cron jobs. This can help you verify that essential tasks are scheduled correctly and identify any unexpected or missing cron events that might be affecting your site's functionality.

Is BugTrace lightweight and will it impact my site's performance?

Absolutely. BugTrace is designed with a minimalist UI and focuses only on essential debugging functionalities. It's lightweight and should not add any noticeable performance overhead to your website's front-end or admin area during normal operation.

What kind of server information can I inspect with BugTrace?

Beyond specific file viewers, BugTrace allows you to see phpinfo() output for detailed PHP configuration, database table information (including size and row count), a list of active browser cookies (read-only), and WordPress transients (read-only). This helps in comprehensive server diagnostics.

How does the admin bar shortcut for the debug log enhance my workflow?

BugTrace adds a convenient shortcut to the WordPress admin bar. This allows you to quickly view, download, or clear the debug.log file from any page within the admin area, speeding up your debugging process significantly.

How does the auto-refresh feature for the debug log work?

The auto-refresh feature periodically reloads the debug log content within the BugTrace interface, allowing you to see new log entries as they are written without needing to manually refresh the page or the entire browser tab. You can also trigger a manual refresh at any time for immediate updates.

更新日志:

1.1.2 New: Error source – a new "Source" column and filter show the plugin, theme, MU plugin or WordPress core that caused each error. New: "View code" shows the lines around an error (read-only), and stack traces are now a collapsible, numbered list. New: Log status bar showing the log path, size, last modified time and live WP_DEBUG, WP_DEBUG_LOG and WP_DEBUG_DISPLAY status. New: Clear messages when the log table is empty (logging off, file missing, file unreadable or log empty), with a one-click "Turn on logging" button. New: Error type counts above the log table; click one to filter the table. New: Your original debug constants are remembered on activation and restored on deactivation. A custom WP_DEBUG_LOG path is never overwritten. Fix: Large debug logs no longer show duplicate rows, wrong timestamps or "Undefined array key" warnings. Fix: Missing debug constants are now added to wp-config.php. This fixes errors being shown on screen and not logged. Sites affected by this are repaired on update. Fix: Fatal error on activation or save when wp-config.php has no "That's all, stop editing!" line. Fix: wp-config.php is now found when WordPress is installed in a subdirectory or wp-config.php is one folder above it. Fix: BugTrace now checks that wp-config.php is still valid PHP after changing it, and puts the original back if not. Fix: A custom WP_DEBUG_LOG path with backslashes (for example a Windows path) is no longer altered. Fix: A WP_DEBUG_LOG path that is a folder, a PHP file or wp-config.php is no longer read, downloaded or cleared as a log. Fix: Activating or saving settings no longer resets the Log Timezone setting. Fix: Settings show the live value of each constant, and constants defined outside wp-config.php are no longer reported as saved. Fix: The admin bar menu is now shown only to users who can manage options, and its labels are translatable. Fix: RTL sites now get the plugin styles. Fix: Site transients show the correct name and expiry. Fix: The Database tab is faster on large sites. Row counts are estimates and marked with "~". Fix: Old Server Info links no longer fail with "The link you followed has expired". Fix: Cron tab shows the next run in the correct timezone and marks overdue events. Fix: "Recoverable fatal error", "Catchable fatal error" and "Strict Standards" entries are no longer listed as "Other". Fix: Log entries with a non-UTC timestamp are no longer merged into the previous entry. Fix: Resetting settings now shows the error when wp-config.php is not writable. Fix: Searching the log waits until you stop typing. Fix: Untranslated strings, a typo, link attributes and other small issues. 1.1.1 New: Plugin data (settings and options) is now removed when the plugin is deleted. Fix: The Exceptions filter in the log table now finds uncaught exceptions. Fix: The log date column header now shows Local or UTC according to the selected timezone. Fix: A duplicate WP_DEBUG_LOG definition is no longer added when the host already defines it. 1.1.0 Fix: PHP notice fixes 1.0.9 New: Search added within the phpinfo() view and the database table list. New: Lightweight syntax highlighting for the wp-config.php and .htaccess viewers. New: Confirmation prompt added before clearing the debug log. New: Performance improvements Fix: Security fixes 1.0.8 Fix: PHP notice fix 1.0.7 New: Setting added to view logs in UTC or WordPress timezone 1.0.6 Fix: The log size is now set automatically based on your PHP memory limit, helping prevent memory issues. Fix: Few css fixes. 1.0.5 New: Error logs are now grouped to reduce repetition and improve readability. 1.0.4 New: Added AI-Powered Help Links for each log entry (ChatGPT, Gemini, Google) for instant error resolution. New: Implemented improved error handling to display a message if WordPress Cron is not working correctly. = 1.0.3 New: Added auto-refresh and manual refresh options for the debug log view, enabling near real-time log monitoring. New: Implemented a 'Copy to Clipboard' action button for the debug log, allowing for easy sharing of log contents. = 1.0.2 New: Added Cookies list (read-only). New: Added Transient list (read-only). New: Added Cron Job list (read-only). New: Added admin bar shortcode to view, download, and clear debug log. = 1.0.1 New: Admin notice on plugin settings page to alert when wp-config.php is not writable. = 1.0.0 Initial release