akmelias

<p>LogIQ is a powerful debug log viewer that makes WordPress debugging easier and more efficient. With its intuitive interface and smart features, you can quickly identify and resolve issues in your WordPress site.</p>
<h4>Key Features</h4>
<ul>
<li><strong>Real-time Log Monitoring</strong>: View WordPress debug logs directly from your admin dashboard</li>
<li><strong>Complex Data Handling</strong>:
<ul>
<li>Beautifully formats and displays complex data types like JSON and arrays</li>
<li>Syntax highlighting for better readability</li>
<li>Collapsible sections for nested data structures</li>
<li>Perfect for debugging webhook payloads, API responses, and complex objects</li>
</ul>
</li>
<li><strong>Smart Log Parsing</strong>:
<ul>
<li>Automatically categorizes logs into different levels (Fatal, Error, Warning, Notice, Deprecated, Info, Debug)</li>
<li>Intelligent detection of data types (JSON, Arrays, Objects)</li>
<li>Context-aware formatting for different log sources</li>
</ul>
</li>
<li><strong>Advanced Filtering</strong>:
<ul>
<li>Filter logs by level, date, and content</li>
<li>Search within specific log types</li>
<li>Combine multiple filters for precise results</li>
<li>Save and load filter presets</li>
</ul>
</li>
<li><strong>Clickable File Links</strong>: Click on file paths in log entries to open them directly in your code editor</li>
<li><strong>Editor Integration</strong>:
<ul>
<li>Supports Visual Studio Code</li>
<li>Supports Sublime Text</li>
<li>Supports PhpStorm</li>
<li>Falls back to file:// protocol if no supported editor is found</li>
</ul>
</li>
<li><strong>Clean Interface</strong>:
<ul>
<li>Modern, responsive design with color-coded log levels</li>
<li>Dark/Light mode support</li>
<li>Customizable column layout</li>
<li>Quick access toolbar</li>
</ul>
</li>
<li><strong>Pagination</strong>: Navigate through large log files with ease</li>
<li><strong>Security</strong>: Built with WordPress security best practices</li>
<li>
<p><strong>Status Dashboard</strong>:</p>
<ul>
<li>Real-time log file size monitoring</li>
<li>Memory usage statistics</li>
<li>PHP version and configuration</li>
<li>WordPress environment details</li>
<li>Server information</li>
<li>Active plugins and themes</li>
</ul>
</li>
<li>
<p><strong>Settings Management</strong>:</p>
<ul>
<li>Configure log retention periods</li>
<li>Set up automatic log rotation</li>
<li>Customize display preferences</li>
<li>Manage user permissions</li>
<li>Configure editor preferences</li>
<li>Set up email notifications</li>
</ul>
</li>
</ul>
<h3>Usage</h3>
<h4>Getting Started</h4>
<p><strong>Access LogIQ</strong><br />
    * Install & Activate LogIQ plugin From WordPress org or Download and put the file inside your plugin directory then activate<br />
    * Go to WordPress admin dashboard<br />
    * Navigate to Tools > LogIQ -> Settings<br />
    * Enable WordPress debug logging and Log to debug.log file and save<br />
    * You’ll see your debug logs displayed in a clean, organized interface</p>
<h4>Using the Log Viewer</h4>
<ol>
<li>
<p><strong>Viewing Logs</strong></p>
<ul>
<li>Logs are displayed in chronological order (newest first)</li>
<li>Each log entry shows:
<ul>
<li>Timestamp</li>
<li>Log level (color-coded)</li>
<li>Message content</li>
<li>File path and line number (if available)</li>
</ul>
</li>
</ul>
</li>
<li>
<p><strong>Filtering Logs</strong></p>
<ul>
<li>Use the filter buttons at the top to show specific log levels:
<ul>
<li>Fatal</li>
<li>Error</li>
<li>Warning</li>
<li>Notice</li>
<li>Deprecated</li>
<li>Info</li>
<li>Debug</li>
</ul>
</li>
<li>Click multiple filters to combine them</li>
<li>Use the search box to find specific text in logs</li>
</ul>
</li>
<li>
<p><strong>Navigating Logs</strong></p>
<ul>
<li>Use pagination controls at the bottom to view older logs</li>
<li>Click the refresh button to see new logs</li>
<li>Use the “Jump to Top” button to return to the latest logs</li>
</ul>
</li>
<li>
<p><strong>View your own log for Debugging</strong></p>
<ul>
<li>Use wordpress’s own error_log</li>
<li>For simple log ex: error_log(‘my own log’)</li>
<li>For complex log data ex: error_log(print_r($complexData, true))</li>
</ul>
</li>
</ol>
<h4>Working with File Links</h4>
<ol>
<li>
<p><strong>Opening Files in Editor</strong></p>
<ul>
<li>Click any file path in a log entry</li>
<li>The file will open in your default code editor</li>
<li>The cursor will automatically move to the relevant line</li>
</ul>
</li>
<li>
<p><strong>Supported Editors</strong></p>
<ul>
<li>Visual Studio Code (recommended)</li>
<li>Sublime Text</li>
<li>PhpStorm</li>
<li>System default text editor (fallback)</li>
</ul>
</li>
<li>
<p><strong>Editor Detection</strong></p>
<ul>
<li>LogIQ automatically detects your installed editors</li>
<li>No configuration needed</li>
<li>Works with the first supported editor found</li>
</ul>
</li>
</ol>
<h4>Advanced Features</h4>
<ol>
<li>
<p><strong>Complex Data Viewing</strong></p>
<ul>
<li>JSON data is automatically formatted and syntax-highlighted</li>
<li>Arrays are displayed in collapsible sections</li>
<li>Click to expand/collapse complex data structures</li>
</ul>
</li>
<li>
<p><strong>Log Management</strong></p>
<ul>
<li>Logs are automatically rotated to prevent large file sizes</li>
<li>Old logs are archived for reference</li>
<li>Clear logs option available in settings</li>
</ul>
</li>
<li>
<p><strong>Security Features</strong></p>
<ul>
<li>Only users with appropriate permissions can view logs</li>
<li>Sensitive data is automatically masked</li>
<li>IP addresses and personal information are protected</li>
</ul>
</li>
</ol>
<h4>Tips & Best Practices</h4>
<ol>
<li>
<p><strong>For Developers</strong></p>
<ul>
<li>Use appropriate log levels for different types of messages</li>
<li>Include relevant context in log messages</li>
<li>Use file paths and line numbers for easier debugging</li>
</ul>
</li>
<li>
<p><strong>For Administrators</strong></p>
<ul>
<li>Regularly check logs for errors and warnings</li>
<li>Set up appropriate user permissions</li>
<li>Monitor log file size and rotation</li>
</ul>
</li>
<li>
<p><strong>Troubleshooting</strong></p>
<ul>
<li>If logs aren’t showing up, verify WP_DEBUG settings</li>
<li>If editor links aren’t working, check editor installation</li>
<li>If performance is slow, consider increasing PHP memory limit</li>
</ul>
</li>
</ol>
<h3>Privacy Policy</h3>
<p>LogIQ does not collect or store any personal data. All log data is stored locally on your server and is only accessible to users with appropriate permissions.</p>
<h3>Additional Information</h3>
<p>For support, feature requests, or bug reports, please visit our <a href="https://github.com/akmelias/log-iq" rel="nofollow ugc">GitHub repository</a> or contact us through our <a href="https://akmelias.com/support" rel="nofollow ugc">support portal</a>.</p>
<h3>Credits</h3>
<p>Developed by AKM Elias</p>


LogIQ

A powerful and user-friendly debug log viewer for WordPress with editor integration.

wpsimpletools

<p>Shows default WP / PHP log file from admin interface, gives the possibility to erase it.<br />
Log viewer is accessible from WP ‘Tools’ menu.</p>


Basic Log Viewer

Does what it says

Useful plugin

Shows default WP / PHP log file from admin interface, gives the possibility to erase it. Only works if debug mode is active.

LogIQ vs Basic Log Viewer