Title: TLloancy Stack Trace Author: Thomas Lloancy Published: Ọwẹ́wẹ̀ 15, 2026 Last modified: Ọwẹ́wẹ̀ 15, 2026 --- Ṣàwárí àwọn plugin ![](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 Láti ọwọ́ [Thomas Lloancy](https://profiles.wordpress.org/tlloancy/) [Ṣe ìgbàsílẹ̀](https://downloads.wordpress.org/plugin/tlloancy-stack-trace.1.0.0.zip) * [Àwọn àlàyé](https://yor.wordpress.org/plugins/tlloancy-stack-trace/#description) * [Àwọn àgbéyẹ̀wò](https://yor.wordpress.org/plugins/tlloancy-stack-trace/#reviews) * [Ìgbéwọlẹ̀](https://yor.wordpress.org/plugins/tlloancy-stack-trace/#installation) * [Ìdàgbàsókè](https://yor.wordpress.org/plugins/tlloancy-stack-trace/#developers) [Ìrànlọ́wọ́](https://wordpress.org/support/plugin/tlloancy-stack-trace/) ## Àpèjúwe 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Ìtumọ̀ Yorùbá: ’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. ## Ìgbéwọlẹ̀ 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. ## FAQ ### 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Ìtumọ̀ Yorùbá: ’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. ### 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Ìtumọ̀ Yorùbá: ’s in-memory SQL (or that pluginÌtumọ̀ Yorùbá:’ s error log) is used instead. ## Àwọn àgbéyẹ̀wò Kò sí àwọn àgbéyẹ̀wò fún plugin yìí. ## Àwọn Olùkópa & Olùgbéejáde “TLloancy Stack Trace” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa sí plugin yìí. Àwọn Olùkópa * [ Thomas Lloancy ](https://profiles.wordpress.org/tlloancy/) [Túmọ̀ “TLloancy Stack Trace” sí èdè rẹ.](https://translate.wordpress.org/projects/wp-plugins/tlloancy-stack-trace) ### Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè? [Ṣàwárí koodu](https://plugins.trac.wordpress.org/browser/tlloancy-stack-trace/), ṣàyẹ̀wò [ibi ìpamọ́ SVN](https://plugins.svn.wordpress.org/tlloancy-stack-trace/), tàbí ṣe àgbékalẹ̀ sí [àkọsílẹ̀ ìdàgbàsókè](https://plugins.trac.wordpress.org/log/tlloancy-stack-trace/) nípasẹ̀ [RSS](https://plugins.trac.wordpress.org/log/tlloancy-stack-trace/?limit=100&mode=stop_on_copy&format=rss). ## Àkọsílẹ̀ àwọn àyípadà #### 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. ## Àkójọpọ̀ Meta * Ẹ̀yà **1.0.0** * Ìgbàgbọ́hùn tó kẹ́yìn **ọjọ́ 4 sẹ́yìn** * Àwọn ìgbéwọlẹ̀ tó ṣiṣẹ́ **Tó kéré sí 10** * Ẹ̀yà WordPress ** 6.0 tàbí ju bẹ́ẹ̀ lọ ** * Dánwò dé **7.1.1** * Ẹ̀yà PHP ** 7.4 tàbí ju bẹ́ẹ̀ lọ ** * Èdè * [English (US)](https://wordpress.org/plugins/tlloancy-stack-trace/) * Àwọn àmì * [crash](https://yor.wordpress.org/plugins/tags/crash/)[debug](https://yor.wordpress.org/plugins/tags/debug/) [error log](https://yor.wordpress.org/plugins/tags/error-log/)[fatal error](https://yor.wordpress.org/plugins/tags/fatal-error/) [memory](https://yor.wordpress.org/plugins/tags/memory/) * [Ìwòye Tó Péye](https://yor.wordpress.org/plugins/tlloancy-stack-trace/advanced/) ## Àwọn ìbò Kò sí ìwádìí tí a tíì fi ránṣẹ́. [Your review](https://wordpress.org/support/plugin/tlloancy-stack-trace/reviews/#new-post) [Wo gbogbo àwọn àgbéyẹ̀wò](https://wordpress.org/support/plugin/tlloancy-stack-trace/reviews/) ## Àwọn Olùkópa * [ Thomas Lloancy ](https://profiles.wordpress.org/tlloancy/) ## Ìrànlọ́wọ́ Nǹkan wà tí o fẹ́ sọ? Ṣé o nílò ìrànlọ́wọ́? [Wo àpéjọ ìrànlọ́wọ́](https://wordpress.org/support/plugin/tlloancy-stack-trace/)