Title: TLloancy Stack Trace Author: Thomas Lloancy Published: 2026 年 9 月 15 日 Last modified: 2026 年 10 月 12 日 --- 搜索插件 ![](https://ps.w.org/tlloancy-stack-trace/assets/banner-772x250.png?rev=3696705) ![](https://ps.w.org/tlloancy-stack-trace/assets/icon-256x256.png?rev=3696705) # TLloancy Stack Trace 作者：[Thomas Lloancy](https://profiles.wordpress.org/tlloancy/) [下载](https://downloads.wordpress.org/plugin/tlloancy-stack-trace.1.0.1.zip) * [详情](https://cn.wordpress.org/plugins/tlloancy-stack-trace/#description) * [评价](https://cn.wordpress.org/plugins/tlloancy-stack-trace/#reviews) * [安装](https://cn.wordpress.org/plugins/tlloancy-stack-trace/#installation) * [开发进展](https://cn.wordpress.org/plugins/tlloancy-stack-trace/#developers) [支持](https://wordpress.org/support/plugin/tlloancy-stack-trace/) ## 描述 TLloancy Stack Trace records PHP fatals (memory exhausted, parse error, and similar), uncaught exceptions, `wp_die` failures, and exceptions that a third-party plugin caught so the site would not white-screen. Each row stores: * The last SQL that actually belongs to the crash (from `$wpdb`, or from a small adapter when a plugin talks to MySQL outside `$wpdb`) * Memory usage, peak, and the configured limit * File and line * The plugin, theme, or core component most likely involved * The request URL Entries live in a dedicated table, under Tools Stack Trace. You can export CSV or clear the log. This is not a debug.log viewer and not a live profiler. Generic log plugins tail PHP or WordPress logs. Stack Trace records **why a request died**: the SQL that belongs to the crash (including plugins that never set `$wpdb->last_query`), memory at the limit, and exceptions another plugin caught so the site would not white-screen. Typical case: an All-in-One WP Migration export that fails with “refresh and try again” while the real cause is a 128M SELECT or a full disk. It is for the morning after: the site crashed, nobody was watching, and you want the cause. #### Plugins that bypass $wpdb Some exporters (All-in-One WP Migration among them) run SQL on `$wpdb->dbh` directly.` $wpdb->last_query` is then empty or already overwritten (cron, Action Scheduler). Stack Trace keeps SQL in memory via adapters and, on failure, can read that plugin’s own error-log `last_query` field. It does not edit third-party files and does not hook their export pipeline as a stage. #### Automatic update failure emails (WordPress 7.2+) A failed automatic plugin update already includes the fatal message, file, and line. Stack Trace adds memory and last SQL from the same loopback check, with a link to the full log. ## 安装 1. Upload the `tlloancy-stack-trace` folder to `/wp-content/plugins/`. 2. Activate the plugin from the Plugins screen. 3. Open the log under Tools Stack Trace. ## 常见问题 ### Does this slow the site down? On a normal request the cost is a shutdown callback that returns immediately unless PHP reports a fatal. A row is written only when something is recorded. Adapters add work only for the target plugin’s AJAX (for example an All-in-One export hop): a header check on success, disk I/O only on failure. ### How many entries are kept? 300 by default. Older rows are pruned when you open the admin page. Override the limit with `TLLST_MAX_ENTRIES` in wp-config.php. `wp_die` rows have their own cap inside that total, 50 by default (`TLLST_MAX_DIE_ENTRIES`), so a run of blocked requests cannot push fatals out of the table. ### Does the plugin change other plugins’ files? No. It does not reorder `active_plugins` and it does not patch files on disk. ### Why is the last SQL not always from $wpdb? If the crash is inside a known custom MySQL client, `$wpdb->last_query` is often unrelated. The adapter’s in-memory SQL (or that plugin’s error log) is used instead. ## 评价 此插件暂无评价。 ## 贡献者及开发者 「TLloancy Stack Trace」是开源软件。 以下人员对此插件做出了贡献。 贡献者 * [ Thomas Lloancy ](https://profiles.wordpress.org/tlloancy/) [帮助将「TLloancy Stack Trace」翻译成简体中文。](https://translate.wordpress.org/projects/wp-plugins/tlloancy-stack-trace) ### 对开发感兴趣吗? 您可以[浏览代码](https://plugins.trac.wordpress.org/browser/tlloancy-stack-trace/)， 查看[SVN仓库](https://plugins.svn.wordpress.org/tlloancy-stack-trace/)，或通过[RSS](https://plugins.trac.wordpress.org/log/tlloancy-stack-trace/?limit=100&mode=stop_on_copy&format=rss) 订阅[开发日志](https://plugins.trac.wordpress.org/log/tlloancy-stack-trace/)。 ## 更新日志 #### 1.0.1 * A handler registered by another plugin that calls Stack Trace back for the same exception no longer loops; the exception is recorded once and the chain continues. * The crash row is written on the current database connection first. Closing and reconnecting happens only when that connection is unusable (“Commands out of sync”, “server has gone away”). * wp_die rows have their own cap, TLLST_MAX_DIE_ENTRIES (50), inside the TLLST_MAX_ENTRIES total, so a run of blocked requests cannot push fatals out of the table. * Code comments in English. #### 1.0.0 * Initial release. * Fatals, swallowed exceptions, and memory crashes with SQL, memory, file/line. * Adapter for All-in-One WP Migration (observe only). * WordPress 7.2 automatic update failure emails include memory and last SQL from the loopback check, per failed plugin. ## 额外信息 * 版本 **1.0.1** * 最后更新：**2 天前** * 活跃安装数量 **不到10** * WordPress 版本 ** 6.0 或更高版本 ** * 已测试的最高版本为 **7.1.3** * PHP 版本 ** 7.4 或更高版本 ** * 语言 * [English (US)](https://wordpress.org/plugins/tlloancy-stack-trace/) * 标签 * [crash](https://cn.wordpress.org/plugins/tags/crash/)[debug](https://cn.wordpress.org/plugins/tags/debug/) [error log](https://cn.wordpress.org/plugins/tags/error-log/)[fatal error](https://cn.wordpress.org/plugins/tags/fatal-error/) [memory](https://cn.wordpress.org/plugins/tags/memory/) * [高级视图](https://cn.wordpress.org/plugins/tlloancy-stack-trace/advanced/) ## 评级 尚未提交反馈。 [您的评价](https://wordpress.org/support/plugin/tlloancy-stack-trace/reviews/#new-post) [查看全部评论](https://wordpress.org/support/plugin/tlloancy-stack-trace/reviews/) ## 贡献者 * [ Thomas Lloancy ](https://profiles.wordpress.org/tlloancy/) ## 支持 有话要说吗？是否需要帮助？ [查看支持论坛](https://wordpress.org/support/plugin/tlloancy-stack-trace/)