內容簡介
**Lumiblog Debug Log Inspector 繁體中文總結:**
Lumiblog Debug Log Inspector 是一個功能強大的品質保證和除錯工具，它監控您的 WordPress debug.log 文件以尋找特定於外掛的錯誤。不同於其他除錯工具，它允許您透過使用簡單易用的設置界面監控任何 WordPress 外掛 - 無需編碼！
### 問題與答案
1. 這款工具的特色有哪些？
- 通用外掛監控：透過簡單的設置頁面添加任何 WordPress 外掛進行監控
- 無需編碼修改：透過 WordPress 管理界面添加/編輯/刪除被監控的外掛
- 實時監控：自動掃描您的 debug.log 文件以查找錯誤
- 視覺狀態指示：色碼管理列顯示（綠色 = 正常，紅色 = 發現錯誤，灰色 = 除錯記錄停用）
- 自動偵測：僅監控目前啟用的外掛的選項
- 外掛特定追踪：每個被監控外掛的獨立狀態
- 最近錯誤顯示：快速診斷的最近錯誤訊息
- 防止重複：智能驗證防止重複添加相同的外掛
- 啟用/停用外掛：在不刪除外掛的情況下切換特定外掛的監控
- 輕量：有效讀取日誌並且對性能影響較小
- 良好組織的程式碼：模組化的文件結構便於維護和自定義
2. 這款工具適用於哪些人群？
- 測試多個外掛的 QA 團隊
- 調試自己外掛的外掛開發人員
- 監控客戶網站的 WordPress 開發人員
- 管理多個 WordPress 安裝的代理團隊
- 任何希望跟踪外掛錯誤的人
3. 如何使用 Lumiblog Debug Log Inspector？
- 安裝並啟用外掛
- 轉至設置 > 日誌檢查器
- 通過提供以下資訊添加您想要監控的任何外掛：
- 外掛名稱（例如，“WooCommerce”）
- 外掛文件路徑（例如，“woocommerce/woocommerce.php”）
- 搜索用語（例如，“woocommerce, wc-”）
- 檢查管理欄以查看實時錯誤狀態
4. 若要有效使用這款工具，需要哪些先決條件？
- 必須啟用 WordPress 的除錯記錄，將以下常數添加到您的 wp-config.php 文件中：
- define( 'WP_DEBUG', true );
- define( 'WP_DEBUG_LOG', true );
5. 如何驗證 Lumiblog Debug Log Inspector 是否正常運作？
- 按照步驟進行：啟用除錯記錄，添加要監控的外掛，生成測試錯誤，檢查結果並查看除錯日誌。
以上為 Lumiblog Debug Log Inspector 的介紹及使用方式。
外掛標籤
開發者團隊
② 後台搜尋「Lumiblog Debug Log Inspector」→ 直接安裝（推薦）
原文外掛簡介
Lumiblog Debug Log Inspector is a powerful quality assurance and debugging tool that monitors your WordPress debug.log file for plugin-specific errors. Unlike other debug tools, it allows you to monitor ANY WordPress plugin through an easy-to-use settings interface – no coding required!
Key Features
Universal Plugin Monitoring: Add any WordPress plugin to monitor through a simple settings page
No Code Editing: Add/edit/delete monitored plugins through the WordPress admin interface
Real-time Monitoring: Automatically scans your debug.log file for errors
Visual Status Indicators: Color-coded admin bar display (Green = OK, Red = Errors Found, Gray = Debug Logging Disabled)
Auto-Detection: Option to only monitor plugins that are currently active
Plugin-Specific Tracking: Individual status for each monitored plugin
Last Error Display: Shows the most recent error message for quick diagnosis
Duplicate Prevention: Smart validation prevents adding the same plugin twice
Enable/Disable Plugins: Toggle monitoring for specific plugins without deleting them
Lightweight: Minimal performance impact with efficient log reading
Well-Organized Code: Modular file structure for easy maintenance and customization
Perfect For
QA Teams testing multiple plugins
Plugin Developers debugging their own plugins
WordPress Developers monitoring client sites
Agency Teams managing multiple WordPress installations
Anyone who wants to keep track of plugin errors
How It Works
Install and activate the plugin
Go to Settings > Log Inspector
Add any plugin you want to monitor by providing:
Plugin Name (e.g., “WooCommerce”)
Plugin File Path (e.g., “woocommerce/woocommerce.php”)
Search Terms (e.g., “woocommerce, wc-“)
Check the admin bar for real-time error status
Requirements
To use this plugin effectively, you need to enable WordPress debug logging by adding these constants to your wp-config.php file:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
Testing the Plugin
To verify Lumiblog Debug Log Inspector is working correctly, follow these steps:
Step 1: Enable Debug Logging
Add to your wp-config.php:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
Step 2: Add a Plugin to Monitor
Go to Settings > Log Inspector
Click “Add New Plugin to Monitor”
Fill in the form with a plugin you have installed (e.g., WooCommerce)
Plugin Name: WooCommerce
Plugin File Path: woocommerce/woocommerce.php
Search Terms: woocommerce, wc-
Click “Add Plugin”
Step 3: Generate a Test Error
Note: Ensure that the test site is running on PHP 8.4+
Add this code snippet inside of any active plugin’s main file:
/**
DEBUG LOG INSPECTOR DEMO – PHP 8.4 Warning Trigger
REMOVE AFTER DEMO/TESTING!
*/
add_action( ‘load-index.php’, function() {
if ( version_compare( PHP_VERSION, ‘8.4.0’, ‘>=’ ) ) {
$test_array = array( ‘name’ => ‘Debug Log Inspector’ );
$undefined_value = $test_array[’email’]; // Triggers warning
error_log( ‘[DLI-DEMO-PHP84] PHP 8.4 warning triggered!’ );
}
});
Reload the site’s admin dashboard to trigger the error
Check your admin bar – it should turn RED
Step 4: View the Debug Log (Optional)
Navigate to wp-content/debug.log to see the actual error entries that were logged.
Clean Up:
Remove the test code you added
Either delete wp-content/debug.log or clear its contents
The admin bar should return to GREEN
Additional Information
Debug Constants
For enhanced debugging, you can also add these optional constants to your wp-config.php:
define( 'SCRIPT_DEBUG', true );
define( 'SAVEQUERIES', true );
define( 'WP_DEBUG_DISPLAY', false ); // Set to false on production sites
For Developers
The plugin is designed to be easily extendable. All classes are well-documented and follow WordPress coding standards. Feel free to fork and customize for your specific needs.
Support
For support, feature requests, or bug reports, please visit the WordPress.org support forums for this plugin.
Contributing
Contributions are welcome! Please visit the plugin’s Github Repo for more information.
