前言介紹
- 這款 WordPress 外掛「oik bwtrace」是 2015-09-07 上架。
- 目前有 20 個安裝啟用數。
- 上一次更新是 2024-09-25，距離現在已有 221 天。
- 外掛最低要求 WordPress 5.0 以上版本才可以安裝。
- 外掛要求網站主機運作至少需要 PHP 版本 5.6 以上。
- 有 1 人給過評分。
- 還沒有人在論壇上發問，可能目前使用數不多，還沒有什麼大問題。
外掛協作開發者
vsgloik | bobbingwide |
外掛標籤
debug | trace | backtrace | ad hoc tracing |
內容簡介
這是一個針對 WordPress 的除錯追蹤外掛，包括特定操作鈎子和過濾器的跟蹤。 主要目的在於幫助 PHP 代碼（插件或主題）的開發，次要功能為追蹤伺服器中事件的順序。 另外，此外掛的特點還包括可以讓您查看正在發生的事情而無需更改任何代碼的特殊跟蹤功能 （即 "Ad hoc tracing"），以及跟踪某些輸出來源的 "string watch" 特性。 此外掛提供了管理介面，以追蹤函數、方法、操作以及過濾器。 不過此外掛不會改變網頁輸出，而是將記錄寫入使用者指定的跟蹤檔案目錄，您可以使用 oik trace 功能協助故障排除，輸出寫入伺服器上的檔案中，當在 live 或 staging 的網站中進行跟蹤時，您應確保跟蹤檔案目錄不公開。
原文外掛簡介
The primary purpose of debug trace is to help in the development of PHP code: plugins or themes.
The primary purpose of action trace is to help you understand the sequence of events in the server.
The primary purpose of ad hoc tracing is to let you see what’s happening without changing any code.
The primary purpose of ‘string watch’ is to track the source of some output.
This plugin provides the admin interface to trace functions and methods and action and filter tracing.
oik bwtrace does not alter the output of your web pages though there are options
which cause some output to be written to the browser during ‘shutdown’ processing.
You can also use the oik trace facilities to assist in problem determination in a live site.
Output is written to files on the server in a user defined trace files directory.
When tracing a live or staging site you should ensure that the trace files directory is not publicly accessible.
Features:
Traces to a defined Trace files directory
Traces ALL server functionality, including AJAX, REST and other background requests
Writes summary trace record for each transaction into Daily Trace summary files
Traces browser transactions separately, if required
Traces AJAX transactions separately, if required
Traces REST requests separately, if required
Traces CLI requests separately, if required
Ability to choose the IP address to trace, defaults to ALL requests
Supports ad hoc tracing of user defined hooks
Action trace counts help you understand the sequence of actions and filters
Provides contextual information
Minimum performance overhead when tracing is not enabled
Tracing can be enabled programmatically
Traces and backtraces PHP Error, Warning and Notice messages
Backtraces deprecated logic messages
Does not require WP_DEBUG to be defined
Does not require SAVEQUERIES to be defined
Dynamically activates trace functions
Implemented as lazy just-in-time code
Can be used during regression testing
Can be activated in wp-config.php and db.php to trace code before WordPress is fully loaded
Plugin does not need to be activated if started programmatically or from wp-config.php
Operates as a standalone plugin
Integrated with oik-lib shared library management
Easy to code APIs: bw_trace2(), bw_backtrace().
API supports multiple trace levels
Ad hoc tracing allows you to:
trace parameters
trace results
trace registered functions
trace the global post
set the priority for the trace hook
debug backtrace hook invocation
perform ‘string watch’ to watch for a particular string
The trace record output can include:
Fully qualified source file name
Trace record count and trace error count
Time stamp
Current filter information
Hook count
Number of database queries that have been performed.
Current post ID
Current and peak memory usage (in bytes)
Files loaded count
Contextual information
The output for action tracing can include trace records showing:
Count of action hooks and filters
Invocation of the ‘wp’ actions
Contents of the global wp_rewrite for the ‘wp’ action
Summary reports at ‘shutdown’
Information about deprecated logic
Information related to Errors, Warnings and Notices
New in v3.4.0
Experimental Performance trace option
Experimental front end links to trace file and daily trace summary
Is there a tutorial?
See this page and short video
Introduction to oik-bwtrace
Can I get support?
Use the contact form on the oik-plugins website.
How can I contribute?
[github bobbingwide oik-bwtrace]
Further reading
If you want to read more about the oik plugins then please visit the
oik plugin
“the oik plugin – for often included key-information”
各版本下載點
- 方法一：點下方版本號的連結下載 ZIP 檔案後，登入網站後台左側選單「外掛」的「安裝外掛」，然後選擇上方的「上傳外掛」，把下載回去的 ZIP 外掛打包檔案上傳上去安裝與啟用。
- 方法二：透過「安裝外掛」的畫面右方搜尋功能，搜尋外掛名稱「oik bwtrace」來進行安裝。
（建議使用方法二，確保安裝的版本符合當前運作的 WordPress 環境。
2.0.5 | 2.0.6 | 2.0.7 | 2.0.8 | 2.0.9 | 2.1.1 | 3.0.0 | 3.2.1 | 3.2.2 | 3.3.1 | 3.4.0 | 3.4.1 | 3.4.2 | 3.4.3 | 3.4.5 | 3.4.6 | 3.4.7 | 3.5.0 | 4.0.0 | trunk | 2.0.11 |
延伸相關外掛（你可能也想知道）
Debug Toolkit 》Debug Toolkit 讓除錯代碼變得更輕鬆且回味無窮，它提供了交互式和有用的工具：, , 更好的 PHP 錯誤介面（來自Whoops）, 更好的變數檢查 - 無需使用 var_dump...。
Hikari Krumo 》Krumo 是一個偵錯工具，相當於 print_r() 和 var_dump()，優點是可以將陣列和物件值折疊起來，這樣就佔用較少的空間，讓我們僅看到複雜資料中真正需要的部分...。
Debug Bar Query Tracer 》Debug Bar Query Tracer 外掛會追蹤所有呼叫 WPDB::query() 進行的資料庫查詢和判斷：, , 哪個外掛導致了這個資料庫查詢（它忽略了所有屬於 WordPress 正常活...。
Development Debug Backtraces 》這個外掛可以在 PHP 產生錯誤時顯示詳細的除錯回溯資訊，除了您在 PHP 安裝時設置的標準錯誤輸出以外。, 這包括 E_ALL，因此可能包含比您預期的更多的錯誤。,...。