Ryan Welcher

We all know that caching is FTW. But, caching can be a nuisance when trying to develop or debug. That’s where this plugin comes in. 
You can bypass any get_transient() calls on a per page basis by clicking the link in the Admin Bar.
Features:
<ol>
<li>Bypass Transients with a single click</li>
<li>Supports Transients saved to the database</li>
<li>Object Cache support – currently only tested with memecached</li>
<li>Will automatically detected any new transients set.</li>
<li>Debug Bar integration to provide details such as lists of known, found and bypassed transients.</li>
</ol>
Usage:
Install and activate the plugin as normal. Suspend transients will loading the appropriate class based on the results <code>wp_using_ext_object_cache()</code>. Anytime a transient set, the plugin will detect it and add it to the 
known list.
Standard Transients ( saved to the database )
When activated, the plugin will retrieve any existing transients from the database and add them to the known transients list.
The Admin Bar will have two new buttons:
<ol>
<li>Bypass Transients: bypasses known transients</li>
<li>Scan Transients: reloads the transients from the database.</li>
</ol>
Object Cached Transients ( i.e memcached ) 
These transients are not stored in the database so the best way to get them is to use the Flush Transients button and reload the page to utilize the transient detection feature of the plugin. 
It may require two page loads; One to detect and add the transient, and then a second to actually bypass it.
Admin Bar buttons:
<ol>
<li>Bypass Transients: bypasses known transients</li>
<li>Flush Transients: Calls wp_object_cache_flush() to invalidate the caches.</li>
</ol>
Disclaimer 
This plugin should NOT be run in a production environment. It is meant for local and MAYBE staging development. By it’s very nature this will slow 
your site down.

Bypass Transients

Bypass any get_transient() calls on a per page basis by clicking the link in the Admin Bar.

Golemiq

Stoil Dobreff

0 Day Analytics helps detect, inspect and respond to PHP and WordPress-level 
errors before they become production incidents. It is optimized for very 
large logs and common debugging/operational workflows.
Core capabilities: 
– Efficiently reads very large (GB-sized) error logs without full-file reads. 
– Error Log Manager with search, filtering, and code-context viewing. 
– Cron Manager: list, edit, run, delete scheduled tasks; advanced filters. 
– Transients Manager: safely list, edit, delete DB transients. 
– Requests Viewer: inspect outgoing HTTP requests. 
– Mail Logger & Composer: record email history, view attachments, compose/send. 
– SMTP configuration and test email support. 
– DB Table Manager: inspect/delete records across tables. 
– Server Info: admin-bar badges and dashboard widget (CPU, memory, disk). 
– Plugin Version Switcher, Code Snippets module, code viewer, CSV export and dark mode. 
– Recovery Mode: one-time recovery links with Slack/Telegram/other channels. 
– Randomize error-log filename for security. 
– PHP Snippets: generate and execute your own snippets when you need them. Shortcodes are supported.
<h3>Short Description</h3>
Real-time error insight and recovery for WordPress — lightweight, fast 
troubleshooting toolkit with log management, cron/transient/request viewers, 
mail logging/composition, SMTP, and a recovery mode.
<h3>Requirements & Compatibility</h3>
<ul>
<li>WordPress 6.0+ (tested up to 6.9)</li>
<li>PHP 7.4+ (compatible with PHP 8+)</li>
<li>Not intended as a multisite recovery tool (see notes below)</li>
</ul>
<h3>Best practices & Security Notes</h3>
<ul>
<li>Keep log files outside the webroot when possible, or restrict access via 
server rules (.htaccess / nginx) to avoid public exposure.</li>
<li>Use a randomized or non-obvious filename for error logs if stored in webroot.</li>
<li>Limit plugin capabilities to trusted administrators (capability checks).</li>
<li>Sanitize and escape all output; use nonces for state-changing actions.</li>
<li>Secure SMTP credentials and prefer TLS/STARTTLS.</li>
<li>Set file permissions tightly (e.g., 600/640) and restrict ownership to the 
web server user.</li>
<li>Backup database/files before bulk delete or run operations.</li>
<li>Disable or restrict high-frequency background polling in high-load sites.</li>
</ul>
<h3>Usage notes & performance</h3>
<ul>
<li>Default error history stores the last 999 errors (adjustable via Screen 
Options) to preserve performance on high-volume logs.</li>
<li>No pagination on error logs by design to avoid repeated full-file reads.</li>
<li>Optional DB-based PHP error logger exists for environments without disk 
logging; consider DB size and retention.</li>
</ul>
<h3>Support & Notes</h3>
<ul>
<li>Recommended: secure log paths and consider randomizing filenames.</li>
<li>Disable unused modules to reduce footprint and attack surface.</li>
<li>Recovery mode is limited on multisite installs due to WP core behavior.</li>
<li>For bugs, feature requests or support, open an issue on the plugin page.</li>
</ul>
Live preview and full details: 
https://wordpress.org/plugins/0-day-analytics/

0 Day Analytics

0 Day Analytics helps detect, inspect and respond to PHP and WordPress-level

Bypass Transients vs 0 Day Analytics