Debugging WordPress shouldn’t be painful.
Most developers deal with debug logs the hard way: SSH into the server, tail -f debug.log, 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.
What Makes LogIQ Different
Most log plugins just dump raw text into a <textarea>. LogIQ actually understands your logs.
- Categorizes every entry by level (Fatal, Error, Warning, Notice, Deprecated, Info, Debug, DB Error)
- Detects duplicate/repeated errors and groups them with a count badge
- Collapses multi-line stack traces so your screen isn’t buried in noise
- Highlights your search term inline across all matching entries
- Shows relative timestamps (“3 minutes ago”) with the full timestamp on hover
- Lets you copy any entry to clipboard in one click
- Opens the exact file and line in VS Code, PhpStorm, or Sublime Text — no copy-pasting paths
Core Features
Smart Log Parsing
Automatically detects PHP Fatal errors, Warnings, Notices, Deprecated calls, Database errors, and custom error_log() 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 ×N 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 .log file or structured .json — 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 file:// 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 manage_options 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.
Perfect For
- WordPress plugin and theme developers
- Agencies managing multiple client sites
- Developers debugging WooCommerce, REST APIs, and third-party integrations
- Anyone who’s tired of
tail -f debug.log
How to Use error_log() with LogIQ
LogIQ reads from WordPress’s standard debug log. Write to it from anywhere in your code:
error_log( 'Something happened' );
For arrays and objects:
error_log( print_r( $my_array, true ) );
For exceptions:
error_log( $exception->getMessage() . ' in ' . $exception->getFile() . ':' . $exception->getLine() );
Privacy Policy
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.
Credits
Developed by AKM Elias. If LogIQ saves you time, consider leaving a review on WordPress.org — it helps more developers find it.
