akmelias

Debugging WordPress shouldn’t be painful.
Most developers deal with debug logs the hard way: SSH into the server, <code>tail -f debug.log</code>, squint at wall-of-text output, scroll endlessly to find the one error that matters. It’s slow, it’s fragile, and it pulls you out of your flow.
LogIQ fixes that.
LogIQ is an intelligent debug log viewer built for WordPress developers. It lives in your admin dashboard, parses your log file automatically, and surfaces exactly what you need — with search, filters, collapsible stack traces, and one-click editor access. No config files. No terminal. No wasted time.
<h4>What Makes LogIQ Different</h4>
Most log plugins just dump raw text into a <code><textarea></code>. LogIQ actually understands your logs.
<ul>
<li>Categorizes every entry by level (Fatal, Error, Warning, Notice, Deprecated, Info, Debug, DB Error)</li>
<li>Detects duplicate/repeated errors and groups them with a count badge</li>
<li>Collapses multi-line stack traces so your screen isn’t buried in noise</li>
<li>Highlights your search term inline across all matching entries</li>
<li>Shows relative timestamps (“3 minutes ago”) with the full timestamp on hover</li>
<li>Lets you copy any entry to clipboard in one click</li>
<li>Opens the exact file and line in VS Code, PhpStorm, or Sublime Text — no copy-pasting paths</li>
</ul>
<h4>Core Features</h4>
Smart Log Parsing 
Automatically detects PHP Fatal errors, Warnings, Notices, Deprecated calls, Database errors, and custom <code>error_log()</code> output. No setup required.
Full-Text Search 
Search across message content, file paths, and timestamps instantly. Matches are highlighted in-place with a count of results.
Level Filters 
Filter by Fatal, Error, Warning, Notice, Deprecated, Info, Debug, or DB Error with a single click. Counts update live with each filter.
Collapsible Stack Traces 
Long stack traces are collapsed by default. Expand only the ones you care about — keeping your view clean and focused.
Duplicate Detection 
Consecutive identical log entries are automatically grouped into a single entry with a <code>×N</code> badge. Stop scrolling past 200 copies of the same warning.
Relative Timestamps 
Log timestamps show as “2 minutes ago”, “1 hour ago” etc. Hover to see the full timestamp. Great for spotting when errors started.
Copy to Clipboard 
One-click copy on every log entry. Paste directly into Slack, a bug report, or a support ticket.
Log Export 
Download your current filtered view as a <code>.log</code> file or structured <code>.json</code> — perfect for sharing with your team or attaching to issue trackers.
Editor Integration 
Click any file path in a log entry to jump directly to that file and line in: 
* Visual Studio Code 
* PhpStorm 
* Sublime Text 
* Falls back to <code>file://</code> if no supported editor is detected
Auto-Refresh 
The log viewer refreshes automatically every 30 seconds so you can watch logs update in real time without touching the page.
Secure by Default 
Only users with <code>manage_options</code> capability can access LogIQ. All AJAX requests are nonce-verified. Sensitive values (passwords, API keys, auth tokens) are masked automatically before display.
Pagination 
Handles large log files gracefully — reads up to 5 MB from the end of the file, paginates entries, and never loads more than needed.
<h4>Perfect For</h4>
<ul>
<li>WordPress plugin and theme developers</li>
<li>Agencies managing multiple client sites</li>
<li>Developers debugging WooCommerce, REST APIs, and third-party integrations</li>
<li>Anyone who’s tired of <code>tail -f debug.log</code></li>
</ul>
<h4>How to Use error_log() with LogIQ</h4>
LogIQ reads from WordPress’s standard debug log. Write to it from anywhere in your code:
<pre><code>error_log( 'Something happened' );
</code></pre>
For arrays and objects:
<pre><code>error_log( print_r( $my_array, true ) );
</code></pre>
For exceptions:
<pre><code>error_log( $exception->getMessage() . ' in ' . $exception->getFile() . ':' . $exception->getLine() );
</code></pre>
<h3>Privacy Policy</h3>
LogIQ does not collect, transmit, or store any personal data outside of your own server. All log data remains local. The plugin does not make any external HTTP requests.
<h3>Credits</h3>
Developed by <a href="https://akmelias.com" rel="nofollow ugc">AKM Elias</a>. If LogIQ saves you time, consider leaving a review on WordPress.org — it helps more developers find it.

LogIQ – Intelligent Debug Log Viewer

Stop digging through raw log files. LogIQ gives WordPress developers a smart, searchable, and beautiful debug log viewer — right inside the admin.

Lukman Nakib

Debug Log Manager Tool is a debug log viewer and WP_DEBUG manager for WordPress. Read, search, group, and clear <code>wp-content/debug.log</code> from inside wp-admin; toggle WP_DEBUG, WP_DEBUG_LOG, WP_DEBUG_DISPLAY, SCRIPT_DEBUG, and SAVEQUERIES from explicit UI controls instead of editing <code>wp-config.php</code>; capture the last fatal error during shutdown; and review slow database queries with their stack trace. Useful as a lightweight alternative to Query Monitor or Debug Bar when you mainly need a clean debug.log reader and explicit debug-constant control.
The plugin focuses on safe first-run behavior: activation does not automatically turn debug mode on, deactivation does not automatically turn it off, and existing debug constants or custom log paths are preserved until you choose to change them.
Use it to inspect the current debug log, search and group log entries, copy useful error details, and make explicit debug configuration changes from the WordPress admin when needed. Advanced tools such as terminal commands, database inspection, Safe Mode, and notifications are available as optional helpers.
<h4>Quick Demo</h4>
<iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/D4K5zsLnILw?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe>
<h4>Key Features</h4>
<ul>
<li>Safe First Run: Activating the plugin does not automatically change WP_DEBUG, WP_DEBUG_LOG, WP_DEBUG_DISPLAY, SCRIPT_DEBUG, SAVEQUERIES, or existing log paths.</li>
<li>Explicit Debug Controls: Review current debug constant values and update them only through intentional UI actions.</li>
<li>Modern Debug Log Viewer: View, search, filter, group, copy, and clear debug log entries from a compact WordPress admin interface.</li>
<li>Readable Timeline Rows: Scan log entries with severity labels, occurrence counts, plugin/source hints, exact timestamps, and copy-as-JSON actions.</li>
<li>Stack Trace Analysis: Format PHP stack traces and database call chains so long fatal errors are easier to read.</li>
<li>Last Fatal Snapshot: Capture the latest fatal error during shutdown and show it in the log screen when wp-admin is available again.</li>
<li>Large Log File Preview: Open the current debug log file inside a modal and safely read the latest 1 MB of large files.</li>
<li>Smooth Upgrade Behavior: Upgrades preserve existing constants and custom debug log locations instead of replacing your current configuration.</li>
<li>Query Inspector: Optionally examine database queries when SAVEQUERIES is enabled, including SQL, caller, execution time, and stack trace details.</li>
<li>WP-CLI Style Terminal: Optionally run guarded WordPress-style commands directly from the browser with command history and auto-completion.</li>
<li>Terminal Settings: Enable or disable terminal access and database commands from a dedicated settings screen.</li>
<li>Safe Mode: Optionally isolate plugin conflicts by keeping selected plugins active and restoring the previous state when Safe Mode is turned off.</li>
<li>Email Notifications: Optionally configure notification email settings, daily summaries, and test email delivery for debug activity.</li>
<li>Admin Bar Debug Toggle: Quickly review and change WP_DEBUG from the WordPress admin bar when you explicitly choose to.</li>
<li>Dashboard Widget: See recent debug log activity from the WordPress dashboard.</li>
<li>Custom Log Path Support: Keep existing custom log paths and use filters to customize the debug log location.</li>
<li>Hardened Admin Routes: AJAX actions use nonce and capability checks, with guarded file path handling for debug log access.</li>
</ul>
<h4>Debug Constants Available</h4>
These constants can be reviewed and changed from the plugin UI. The plugin does not change them on activation or deactivation.
<ul>
<li>WP_DEBUG – Enables WordPress debug mode</li>
<li>WP_DEBUG_LOG – Saves errors to the configured debug log destination</li>
<li>SCRIPT_DEBUG – Uses development versions of core JS and CSS files</li>
<li>WP_DEBUG_DISPLAY – Controls whether debug messages display on screen</li>
<li>SAVEQUERIES – Saves database queries for analysis</li>
</ul>
<h4>Developer Tools</h4>
<ul>
<li>Terminal Commands: Optionally use WP-CLI style commands like <code>wp core version</code> or <code>wp plugin list</code></li>
<li>Database Explorer: Optionally run SELECT queries and view results in a formatted table</li>
<li>Stack Trace Analysis: Visualize error stack traces for easier debugging</li>
<li>Hook Inspector: View all registered hooks and their callbacks</li>
<li>Environment Detection: Development features are automatically hidden in production</li>
<li>Copy JSON: Copy structured log entries for support tickets or developer handoff</li>
<li>File Viewer: Inspect the debug log file without leaving the WordPress admin screen</li>
</ul>
<blockquote>
Developer API: Use filters like <code>wp_dlct_log_file_path</code> and <code>dlct_debug_file_path</code> to customize log path behavior.
</blockquote>
Please note: Configuration changes are made only by explicit UI actions. Deactivating the plugin does not automatically restore, remove, enable, or disable WordPress debug constants.

Debug Log Manager Tool

Awesome!

Helps us a lot with development :)

it's exactly what i am after for. instead of connecting to ftp, opening wp-config.php, editing the constants, saving, uploading, reloading site, opening debug.log and deleting it and so on … you simple enable the toggle and look into the logs right in wordpress with nice styling so you can easily distinguish between warning and errors. 
in the future i would like to see more toggles for instance for WP_DEBUG_DISPLAY. for some reason this is missing?! 

simple but good


My go-to debugging plugin for 500 internal server errors and anything that's trickier to track. Good job.


Super useful


Fantastic plugin with an easy interface for browsing. Thank you so much for making it available for free!


Fantastic & easy to use.


The plugin used to work very well, but with the latest update the debug log cannot be cleaned. This has been reported as a bug 2 months ago with no response and no other update. This is why I'm giving the plugin 2 stars. There are other plugins that work better.



--- EDIT ---



Recently I tested the plugin again and it has improved by a lot. I see new functions and - so far - zero bugs. Well done. I improve my rating. Keep up the good work.


Much improved over time


Using this plugin for more than 3 years, and its my favourite one to debug!


Great plugin

Read, search, and clear WordPress debug logs from wp-admin. Toggle WP_DEBUG and inspect errors without FTP.

LogIQ – Intelligent Debug Log Viewer vs Debug Log Manager Tool