[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fffPfNUBMOn0AwXNP2UGaH977Szx9l0YicmsG5E7Xw5E":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":13,"last_updated":14,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":18,"homepage":24,"download_link":25,"security_score":11,"vuln_count":13,"unpatched_count":13,"last_vuln_date":26,"fetched_at":27,"vulnerabilities":28,"developer":29,"crawl_stats":26,"alternatives":35,"analysis":130,"fingerprints":204},"wp-output-log-file","WP Output Log File","1.2.2","Reiji Sato","https:\u002F\u002Fprofiles.wordpress.org\u002Freiji-sato\u002F","\u003Cp>Manage WordPress log files independently of WP_DEBUG mode.\u003Cbr \u002F>\nYou can specify the output directory and file name, download log files, and delete them as needed.\u003C\u002Fp>\n\u003Cp>By specifying a date format in the file name, you can split logs daily or monthly.\u003C\u002Fp>\n","Manage log files with custom directory and filename. Download and delete logs regardless of WP_DEBUG.",100,2312,0,"","6.7.5","5.0","5.6",[19,20,21,22,23],"debug","debugging","developer","error","log","https:\u002F\u002Fgithub.com\u002Fsofp\u002Fwp-output-log-file","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-output-log-file.1.2.2.zip",null,"2026-03-15T10:48:56.248Z",[],{"slug":30,"display_name":7,"profile_url":8,"plugin_count":31,"total_installs":11,"avg_security_score":11,"avg_patch_time_days":32,"trust_score":33,"computed_at":34},"reiji-sato",2,30,94,"2026-04-04T13:52:09.685Z",[36,57,72,92,112],{"slug":37,"name":38,"version":39,"author":40,"author_profile":41,"description":42,"short_description":43,"active_installs":44,"downloaded":45,"rating":13,"num_ratings":13,"last_updated":46,"tested_up_to":47,"requires_at_least":48,"requires_php":49,"tags":50,"homepage":54,"download_link":55,"security_score":11,"vuln_count":13,"unpatched_count":13,"last_vuln_date":26,"fetched_at":56},"log-iq","LogIQ","1.0.3","akmelias","https:\u002F\u002Fprofiles.wordpress.org\u002Fakmelias\u002F","\u003Cp>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.\u003C\u002Fp>\n\u003Ch4>Key Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Real-time Log Monitoring\u003C\u002Fstrong>: View WordPress debug logs directly from your admin dashboard\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Complex Data Handling\u003C\u002Fstrong>:\n\u003Cul>\n\u003Cli>Beautifully formats and displays complex data types like JSON and arrays\u003C\u002Fli>\n\u003Cli>Syntax highlighting for better readability\u003C\u002Fli>\n\u003Cli>Collapsible sections for nested data structures\u003C\u002Fli>\n\u003Cli>Perfect for debugging webhook payloads, API responses, and complex objects\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Smart Log Parsing\u003C\u002Fstrong>:\n\u003Cul>\n\u003Cli>Automatically categorizes logs into different levels (Fatal, Error, Warning, Notice, Deprecated, Info, Debug)\u003C\u002Fli>\n\u003Cli>Intelligent detection of data types (JSON, Arrays, Objects)\u003C\u002Fli>\n\u003Cli>Context-aware formatting for different log sources\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Advanced Filtering\u003C\u002Fstrong>:\n\u003Cul>\n\u003Cli>Filter logs by level, date, and content\u003C\u002Fli>\n\u003Cli>Search within specific log types\u003C\u002Fli>\n\u003Cli>Combine multiple filters for precise results\u003C\u002Fli>\n\u003Cli>Save and load filter presets\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Clickable File Links\u003C\u002Fstrong>: Click on file paths in log entries to open them directly in your code editor\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Editor Integration\u003C\u002Fstrong>:\n\u003Cul>\n\u003Cli>Supports Visual Studio Code\u003C\u002Fli>\n\u003Cli>Supports Sublime Text\u003C\u002Fli>\n\u003Cli>Supports PhpStorm\u003C\u002Fli>\n\u003Cli>Falls back to file:\u002F\u002F protocol if no supported editor is found\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Clean Interface\u003C\u002Fstrong>:\n\u003Cul>\n\u003Cli>Modern, responsive design with color-coded log levels\u003C\u002Fli>\n\u003Cli>Dark\u002FLight mode support\u003C\u002Fli>\n\u003Cli>Customizable column layout\u003C\u002Fli>\n\u003Cli>Quick access toolbar\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Pagination\u003C\u002Fstrong>: Navigate through large log files with ease\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Security\u003C\u002Fstrong>: Built with WordPress security best practices\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Status Dashboard\u003C\u002Fstrong>:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Real-time log file size monitoring\u003C\u002Fli>\n\u003Cli>Memory usage statistics\u003C\u002Fli>\n\u003Cli>PHP version and configuration\u003C\u002Fli>\n\u003Cli>WordPress environment details\u003C\u002Fli>\n\u003Cli>Server information\u003C\u002Fli>\n\u003Cli>Active plugins and themes\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Settings Management\u003C\u002Fstrong>:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Configure log retention periods\u003C\u002Fli>\n\u003Cli>Set up automatic log rotation\u003C\u002Fli>\n\u003Cli>Customize display preferences\u003C\u002Fli>\n\u003Cli>Manage user permissions\u003C\u002Fli>\n\u003Cli>Configure editor preferences\u003C\u002Fli>\n\u003Cli>Set up email notifications\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Ch4>Getting Started\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>Access LogIQ\u003C\u002Fstrong>\u003Cbr \u002F>\n    * Install & Activate LogIQ plugin From WordPress org or Download and put the file inside your plugin directory then activate\u003Cbr \u002F>\n    * Go to WordPress admin dashboard\u003Cbr \u002F>\n    * Navigate to Tools > LogIQ -> Settings\u003Cbr \u002F>\n    * Enable WordPress debug logging and Log to debug.log file and save\u003Cbr \u002F>\n    * You’ll see your debug logs displayed in a clean, organized interface\u003C\u002Fp>\n\u003Ch4>Using the Log Viewer\u003C\u002Fh4>\n\u003Col>\n\u003Cli>\n\u003Cp>\u003Cstrong>Viewing Logs\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Logs are displayed in chronological order (newest first)\u003C\u002Fli>\n\u003Cli>Each log entry shows:\n\u003Cul>\n\u003Cli>Timestamp\u003C\u002Fli>\n\u003Cli>Log level (color-coded)\u003C\u002Fli>\n\u003Cli>Message content\u003C\u002Fli>\n\u003Cli>File path and line number (if available)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Filtering Logs\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Use the filter buttons at the top to show specific log levels:\n\u003Cul>\n\u003Cli>Fatal\u003C\u002Fli>\n\u003Cli>Error\u003C\u002Fli>\n\u003Cli>Warning\u003C\u002Fli>\n\u003Cli>Notice\u003C\u002Fli>\n\u003Cli>Deprecated\u003C\u002Fli>\n\u003Cli>Info\u003C\u002Fli>\n\u003Cli>Debug\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Click multiple filters to combine them\u003C\u002Fli>\n\u003Cli>Use the search box to find specific text in logs\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Navigating Logs\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Use pagination controls at the bottom to view older logs\u003C\u002Fli>\n\u003Cli>Click the refresh button to see new logs\u003C\u002Fli>\n\u003Cli>Use the “Jump to Top” button to return to the latest logs\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>View your own log for Debugging\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Use wordpress’s own error_log\u003C\u002Fli>\n\u003Cli>For simple log ex: error_log(‘my own log’)\u003C\u002Fli>\n\u003Cli>For complex log data ex: error_log(print_r($complexData, true))\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Working with File Links\u003C\u002Fh4>\n\u003Col>\n\u003Cli>\n\u003Cp>\u003Cstrong>Opening Files in Editor\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Click any file path in a log entry\u003C\u002Fli>\n\u003Cli>The file will open in your default code editor\u003C\u002Fli>\n\u003Cli>The cursor will automatically move to the relevant line\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Supported Editors\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Visual Studio Code (recommended)\u003C\u002Fli>\n\u003Cli>Sublime Text\u003C\u002Fli>\n\u003Cli>PhpStorm\u003C\u002Fli>\n\u003Cli>System default text editor (fallback)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Editor Detection\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>LogIQ automatically detects your installed editors\u003C\u002Fli>\n\u003Cli>No configuration needed\u003C\u002Fli>\n\u003Cli>Works with the first supported editor found\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Advanced Features\u003C\u002Fh4>\n\u003Col>\n\u003Cli>\n\u003Cp>\u003Cstrong>Complex Data Viewing\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>JSON data is automatically formatted and syntax-highlighted\u003C\u002Fli>\n\u003Cli>Arrays are displayed in collapsible sections\u003C\u002Fli>\n\u003Cli>Click to expand\u002Fcollapse complex data structures\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Log Management\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Logs are automatically rotated to prevent large file sizes\u003C\u002Fli>\n\u003Cli>Old logs are archived for reference\u003C\u002Fli>\n\u003Cli>Clear logs option available in settings\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Security Features\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Only users with appropriate permissions can view logs\u003C\u002Fli>\n\u003Cli>Sensitive data is automatically masked\u003C\u002Fli>\n\u003Cli>IP addresses and personal information are protected\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Tips & Best Practices\u003C\u002Fh4>\n\u003Col>\n\u003Cli>\n\u003Cp>\u003Cstrong>For Developers\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Use appropriate log levels for different types of messages\u003C\u002Fli>\n\u003Cli>Include relevant context in log messages\u003C\u002Fli>\n\u003Cli>Use file paths and line numbers for easier debugging\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>For Administrators\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Regularly check logs for errors and warnings\u003C\u002Fli>\n\u003Cli>Set up appropriate user permissions\u003C\u002Fli>\n\u003Cli>Monitor log file size and rotation\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Troubleshooting\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>If logs aren’t showing up, verify WP_DEBUG settings\u003C\u002Fli>\n\u003Cli>If editor links aren’t working, check editor installation\u003C\u002Fli>\n\u003Cli>If performance is slow, consider increasing PHP memory limit\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Privacy Policy\u003C\u002Fh3>\n\u003Cp>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.\u003C\u002Fp>\n\u003Ch3>Additional Information\u003C\u002Fh3>\n\u003Cp>For support, feature requests, or bug reports, please visit our \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fakmelias\u002Flog-iq\" rel=\"nofollow ugc\">GitHub repository\u003C\u002Fa> or contact us through our \u003Ca href=\"https:\u002F\u002Fakmelias.com\u002Fsupport\" rel=\"nofollow ugc\">support portal\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Credits\u003C\u002Fh3>\n\u003Cp>Developed by AKM Elias\u003C\u002Fp>\n","A powerful and user-friendly debug log viewer for WordPress with editor integration.",10,495,"2025-07-06T14:41:00.000Z","6.8.5","5.8","7.4",[20,51,52,53],"developer-tools","error-log","log-viewer","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Flog-iq\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flog-iq.1.0.3.zip","2026-03-15T15:16:48.613Z",{"slug":58,"name":59,"version":60,"author":61,"author_profile":62,"description":63,"short_description":64,"active_installs":13,"downloaded":65,"rating":13,"num_ratings":13,"last_updated":14,"tested_up_to":47,"requires_at_least":66,"requires_php":67,"tags":68,"homepage":70,"download_link":71,"security_score":11,"vuln_count":13,"unpatched_count":13,"last_vuln_date":26,"fetched_at":27},"debug-suite","Debug Suite","1.1.1","Kamruzzaman","https:\u002F\u002Fprofiles.wordpress.org\u002Fkzamanbd\u002F","\u003Cp>Debug Suite is a comprehensive WordPress development toolkit that transforms how developers debug and maintain WordPress sites. Built with enterprise-grade architecture and modern development practices, it provides powerful debugging capabilities while maintaining high performance and code quality.\u003C\u002Fp>\n\u003Ch4>🚀 Key Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Advanced Log Management\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Real-time log file monitoring\u003C\u002Fli>\n\u003Cli>Configurable log levels and filtering\u003C\u002Fli>\n\u003Cli>Searchable log entries with context\u003C\u002Fli>\n\u003Cli>Log file rotation and cleanup\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Error Tracking & Debugging\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Detailed error tracking and reporting\u003C\u002Fli>\n\u003Cli>Stack trace analysis\u003C\u002Fli>\n\u003Cli>Query debugging and optimization\u003C\u002Fli>\n\u003Cli>Performance profiling\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Developer Tools\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Built-in code editor with syntax highlighting\u003C\u002Fli>\n\u003Cli>File system management interface\u003C\u002Fli>\n\u003Cli>Database query analyzer\u003C\u002Fli>\n\u003Cli>REST API debugging tools\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Modern Architecture\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Dependency injection container\u003C\u002Fli>\n\u003Cli>Service layer pattern\u003C\u002Fli>\n\u003Cli>React\u002FTypeScript frontend\u003C\u002Fli>\n\u003Cli>Enterprise-grade codebase\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>🎯 Perfect for\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>WordPress developers building complex applications\u003C\u002Fli>\n\u003Cli>Agency developers managing multiple sites\u003C\u002Fli>\n\u003Cli>DevOps teams monitoring WordPress installations\u003C\u002Fli>\n\u003Cli>Site administrators debugging production issues\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>🛡️ Security First\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Secure by default – strict file permissions\u003C\u002Fli>\n\u003Cli>Role-based access control\u003C\u002Fli>\n\u003Cli>Sanitized and escaped data handling\u003C\u002Fli>\n\u003Cli>WordPress security best practices\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>🔧 Technical Requirements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>WordPress 5.7 or higher\u003C\u002Fli>\n\u003Cli>PHP 8.1 or higher\u003C\u002Fli>\n\u003Cli>Modern browser with JavaScript enabled\u003C\u002Fli>\n\u003Cli>Write permissions for log directories\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>🌟 Pro Features (Coming Soon)\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Remote debugging capabilities\u003C\u002Fli>\n\u003Cli>Advanced performance profiling\u003C\u002Fli>\n\u003Cli>Team collaboration tools\u003C\u002Fli>\n\u003Cli>Custom logging integrations\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Development\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fkzamanbd\u002Fdebug-suite\" rel=\"nofollow ugc\">GitHub Repository\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fkzaman.me\u002Fplugins\u002Fdebug-suite\u002Fdocs\" rel=\"nofollow ugc\">Documentation\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fkzamanbd\u002Fdebug-suite\u002Fissues\" rel=\"nofollow ugc\">Issue Tracker\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Credits\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Built with modern WordPress development practices\u003C\u002Fli>\n\u003Cli>Uses React and TypeScript for the frontend\u003C\u002Fli>\n\u003Cli>Implements PSR standards and enterprise patterns\u003C\u002Fli>\n\u003Cli>Special thanks to the WordPress development community\u003C\u002Fli>\n\u003C\u002Ful>\n","A powerful, enterprise-grade debugging toolkit for WordPress developers with advanced log management, error tracking, and development tools.",319,"6.8","8.1",[19,20,51,69,52],"development","https:\u002F\u002Fkzaman.me\u002Fplugins\u002Fdebug-suite?utm_source=wp-plugins&utm_campaign=plugin-uri&utm_medium=wp-dash","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-suite.1.1.1.zip",{"slug":73,"name":74,"version":75,"author":76,"author_profile":77,"description":78,"short_description":79,"active_installs":80,"downloaded":81,"rating":82,"num_ratings":83,"last_updated":84,"tested_up_to":85,"requires_at_least":48,"requires_php":86,"tags":87,"homepage":14,"download_link":88,"security_score":89,"vuln_count":90,"unpatched_count":13,"last_vuln_date":91,"fetched_at":56},"debug-log-viewer","Debug Log Viewer","2.1","Oleksandr Lysyi","https:\u002F\u002Fprofiles.wordpress.org\u002Flysyiweb\u002F","\u003Cp>Debug Log Viewer: Your Essential WordPress Debugging Tool\u003C\u002Fp>\n\u003Cp>Tired of struggling to access and understand your WordPress debug.log file?  Debug Log Viewer simplifies WordPress debugging by providing a user-friendly interface to view, search, and manage your debug.log directly within your WordPress admin area.  It’s the perfect solution for WordPress developers, site administrators, and anyone needing to quickly identify and resolve website issues.\u003C\u002Fp>\n\u003Cp>Gain Real-Time Insights into Your WordPress Site Health\u003C\u002Fp>\n\u003Cp>This plugin is designed to provide you with instant visibility into the inner workings of your WordPress website. By tracking errors, warnings, and deprecated function notices in real-time, Debug Log Viewer empowers you to proactively maintain a healthy and stable WordPress environment.\u003C\u002Fp>\n\u003Cp>Key Features for Efficient WordPress Debugging:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Real-Time Log Viewer:  Monitor your WordPress debug.log file in real-time, directly from your WordPress dashboard. No more hunting for files via FTP or cPanel!\u003C\u002Fli>\n\u003Cli>Easy Debug Log Access:  Access and view your full WordPress debug log within a clean and intuitive interface.\u003C\u002Fli>\n\u003Cli>Search and Filtering: Quickly find specific log entries with powerful search and filtering options. Filter by error type, keywords, or date (future feature) to pinpoint issues fast.\u003C\u002Fli>\n\u003Cli>Pagination: Navigate through large debug logs with ease using pagination, ensuring smooth performance even with extensive logs.\u003C\u002Fli>\n\u003Cli>Email Alerts for Critical Errors:  Get immediate email alerts when new errors are logged, allowing you to address critical issues before they impact your users (future feature: configurable severity levels).\u003C\u002Fli>\n\u003Cli>Flexible Settings Panel:\n\u003Cul>\n\u003Cli>Control WP_DEBUG Constants:  Enable or disable WP_DEBUG and WP_DEBUG_LOG constants directly from the plugin settings, without editing wp-config.php.\u003C\u002Fli>\n\u003Cli>Customize Logging Options: Configure your debug log settings to match your specific needs.\u003C\u002Fli>\n\u003Cli>Tailor Your Error Tracking:  Personalize your debugging experience through plugin settings.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Custom Log Path Support:  If you’ve defined a custom path for your debug.log file (e.g., using define( ‘WP_DEBUG_LOG’, ABSPATH . ‘wp-content\u002Flogs\u002Fdebug.log’ );), Debug Log Viewer automatically detects and reads from it.\u003C\u002Fli>\n\u003Cli>Automatic Log Cleanup:  Schedule automatic cleanup to prevent your debug.log from growing too large and consuming disk space. Keep your site running smoothly with automatic maintenance at 50MB threshold.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Benefits of Using Debug Log Viewer:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Save Time and  Effort: Stop wasting time manually accessing and parsing your debug log file. Debug Log Viewer puts all the information you need at your fingertips within WordPress admin.\u003C\u002Fli>\n\u003Cli>Faster Error Detection: Real-time monitoring and email alerts help you catch errors as they happen, minimizing potential downtime.\u003C\u002Fli>\n\u003Cli>Simplified WordPress Troubleshooting:  Quickly identify the source of errors and warnings to streamline your WordPress troubleshooting process.\u003C\u002Fli>\n\u003Cli>Improved Website Stability: Proactive error monitoring and resolution contribute to a more stable and reliable WordPress website.\u003C\u002Fli>\n\u003Cli>User-Friendly Interface:  No coding skills required!  Debug Log Viewer is designed for ease of use, making debug log management accessible to everyone.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Debug Log Viewer Pro Features:\u003C\u002Fp>\n\u003Cp>Upgrade to Pro for advanced debugging capabilities:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Advanced Email Alert Customization: Choose specific error levels to monitor and reduce notification noise.\u003C\u002Fli>\n\u003Cli>CSV Export: Export debug log data for analysis, reporting, or sharing with team members.\u003C\u002Fli>\n\u003Cli>Custom Date Range Filtering: Filter log entries by specific time periods for targeted troubleshooting.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Who is Debug Log Viewer For?\u003C\u002Fp>\n\u003Cul>\n\u003Cli>WordPress developers\u003C\u002Fli>\n\u003Cli>Website administrators\u003C\u002Fli>\n\u003Cli>Freelancers managing client sites\u003C\u002Fli>\n\u003Cli>Anyone who wants an easy way to monitor WordPress errors and improve website health\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Tested up to\u003C\u002Fh3>\n\u003Cp>WordPress Version: 6.9\u003Cbr \u002F>\nPHP Version: 8.3.9\u003C\u002Fp>\n","Effortlessly view, search, filter and manage your WordPress debug.log in the admin dashboard. Real-time monitoring and email alerts",1000,11501,80,3,"2026-03-02T06:29:00.000Z","6.9.4","7.2",[19,20,52,23],"https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-log-viewer.2.1.zip",99,1,"2025-10-29 00:00:00",{"slug":93,"name":94,"version":95,"author":96,"author_profile":97,"description":98,"short_description":99,"active_installs":100,"downloaded":101,"rating":13,"num_ratings":13,"last_updated":102,"tested_up_to":103,"requires_at_least":104,"requires_php":14,"tags":105,"homepage":109,"download_link":110,"security_score":89,"vuln_count":90,"unpatched_count":13,"last_vuln_date":111,"fetched_at":56},"developer-loggers-for-simple-history","Developer Loggers for Simple History","0.5.1","Pär Thernström","https:\u002F\u002Fprofiles.wordpress.org\u002Feskapism\u002F","\u003Cp>Bring more loggers to \u003Ca href=\"https:\u002F\u002Fsimple-history.com\" rel=\"nofollow ugc\">WordPress user history plugin Simple History\u003C\u002Fa>.\u003Cbr \u002F>\nThat are useful for developers during development of a site or to maintain a live site.\u003C\u002Fp>\n\u003Ch3>Important\u003C\u002Fh3>\n\u003Cp>Please note that this plugin is no longer actively maintained and only receives security fixes.\u003C\u002Fp>\n\u003Ch3>Modern and up to date alternatives\u003C\u002Fh3>\n\u003Cp>For an up to date alternative please see the \u003Ca href=\"https:\u002F\u002Fsimple-history.com\u002Fadd-ons\u002Fdebug-and-monitor\u002F\" rel=\"nofollow ugc\">Debug & Monitor add-on\u003C\u002Fa> which logs WP REST API requests, sent emails, HTTP API requests, and WP cron jobs.\u003C\u002Fp>\n\u003Ch3>Get more features with Simple History Premium\u003C\u002Fh3>\n\u003Cp>Need advanced WordPress audit logging capabilities? Simple History Premium extends your site monitoring with powerful features:\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Enhanced WordPress Activity Logging:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Advanced Analytics Dashboard\u003C\u002Fstrong> – Comprehensive stats and visual activity tracking\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Custom Event Logging\u003C\u002Fstrong> – Add manual entries and notifications to your audit trail\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Stealth Mode\u003C\u002Fstrong> – Control user access with granular permissions\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Flexible Log Retention\u003C\u002Fstrong> – Configure automatic cleanup or keep logs indefinitely\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Data Export Tools\u003C\u002Fstrong> – Export logs in CSV\u002FJSON format for analysis\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Security Features\u003C\u002Fstrong> – IP anonymization and login attempt location tracking\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fsimple-history.com\u002Fpremium\u002F\" rel=\"nofollow ugc\">» \u003Cstrong>Get Simple History Premium\u003C\u002Fstrong>\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>Included loggers and plugins\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Post to Slack\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>All your events is posted to a \u003Ca href=\"https:\u002F\u002Fslack.com\u002F\" rel=\"nofollow ugc\">Slack\u003C\u002Fa> channel of your choice, using an \u003Ca href=\"https:\u002F\u002Fapi.slack.com\u002Fincoming-webhooks\" rel=\"nofollow ugc\">incoming webhook\u003C\u002Fa>. Yes, with this plugin enabled\u003Cbr \u002F>\nthere is no need what so ever to ever leave Slack to see what’s happening on your site or the site of your\u003Cbr \u002F>\nclients or… well, on any site where you have Simple Histor and this plugin enabled.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>WP_Mail-logger\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>See all mails sent with wp_mail(), no matter what the recipient address is.\u003Cbr \u002F>\nchangelog\u003C\u002Fp>\n\u003Cp>\u003Cstrong>404 logger\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>View page visits that load the 404 template.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>JavaScript error logger\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>See what JavaScript errors users that visit your site is getting.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>SystemLog logger\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Log all messages from Simple History to the syslog on the server. With this logger enabled there is no need to use the beautiful GUI of Simple History ;).\u003C\u002Fp>\n\u003Cp>\u003Cstrong>HTTP API logger\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Log all usage of HTTP calls from functions like wp_remote_post() and wp_remote_get().\u003C\u002Fp>\n\u003Cp>You can the URL requested, the arguments posted and the full returned result, including server headers.\u003C\u002Fp>\n\u003Cp>The time for the request to complete is also logged. Great for debugging!\u003C\u002Fp>\n","Useful loggers for SimpleHistory for developers during development of a site or to maintain a live site.",400,7569,"2025-09-15T07:32:00.000Z","6.4.8","4.4",[20,21,106,107,108],"email","logging","simple-history","https:\u002F\u002Fgithub.com\u002Fbonny\u002FDeveloper-Loggers-for-Simple-History","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdeveloper-loggers-for-simple-history.0.5.1.zip","2025-09-16 00:00:00",{"slug":113,"name":114,"version":115,"author":116,"author_profile":117,"description":118,"short_description":119,"active_installs":120,"downloaded":121,"rating":11,"num_ratings":90,"last_updated":122,"tested_up_to":85,"requires_at_least":123,"requires_php":49,"tags":124,"homepage":128,"download_link":129,"security_score":11,"vuln_count":13,"unpatched_count":13,"last_vuln_date":26,"fetched_at":56},"error-logs-emailer-for-woocommerce","Error Logs Emailer for WooCommerce","1.2.4","Michal Slepko","https:\u002F\u002Fprofiles.wordpress.org\u002Fmslepko\u002F","\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Frootscopeltd\u002Fwc-error-logs-emailer\" rel=\"nofollow ugc\">Error Logs Emailer for WooCommerce\u003C\u002Fa> is a free plugin to send fatal error logged by WooCommerce\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Know what errors are happening on your site without constantly checking the logs\u003C\u002Fli>\n\u003Cli>Set the email where error logs should be sent if it’s not a site admin\u003C\u002Fli>\n\u003Cli>Add multiple email addresses\u003C\u002Fli>\n\u003Cli>Emails are sent at 5AM\u003C\u002Fli>\n\u003C\u002Ful>\n","Sends the previous day's WooCommerce fatal error log to specified email(s) using Action Scheduler.",20,1254,"2026-01-22T00:01:00.000Z","6.0",[19,125,52,126,127],"developers","errors","woocommerce","https:\u002F\u002Fgithub.com\u002Frootscopeltd\u002Fwc-error-logs-emailer","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ferror-logs-emailer-for-woocommerce.1.2.4.zip",{"attackSurface":131,"codeSignals":152,"taintFlows":166,"riskAssessment":194,"analyzedAt":203},{"hooks":132,"ajaxHandlers":148,"restRoutes":149,"shortcodes":150,"cronEvents":151,"entryPointCount":13,"unprotectedCount":13},[133,139,143],{"type":134,"name":135,"callback":136,"file":137,"line":138},"action","admin_menu","add_plugin_page","includes\\class-wolf-admin.php",25,{"type":134,"name":140,"callback":141,"file":137,"line":142},"admin_init","page_init",26,{"type":134,"name":144,"callback":145,"file":146,"line":147},"init","wo_log_load_textdomain","wp-output-log-file.php",56,[],[],[],[],{"dangerousFunctions":153,"sqlUsage":154,"outputEscaping":156,"fileOperations":164,"externalRequests":13,"nonceChecks":90,"capabilityChecks":13,"bundledLibraries":165},[],{"prepared":13,"raw":13,"locations":155},[],{"escaped":157,"rawEcho":31,"locations":158},22,[159,162],{"file":137,"line":160,"context":161},49,"raw output",{"file":137,"line":163,"context":161},50,4,[],[167,186],{"entryPoint":168,"graph":169,"unsanitizedCount":13,"severity":185},"load (includes\\class-wolf-admin.php:264)",{"nodes":170,"edges":182},[171,176],{"id":172,"type":173,"label":174,"file":137,"line":175},"n0","source","$_GET (x2)",270,{"id":177,"type":178,"label":179,"file":137,"line":180,"wp_function":181},"n1","sink","header() [Header Injection]",289,"header",[183],{"from":172,"to":177,"sanitized":184},true,"low",{"entryPoint":187,"graph":188,"unsanitizedCount":13,"severity":185},"\u003Cclass-wolf-admin> (includes\\class-wolf-admin.php:0)",{"nodes":189,"edges":192},[190,191],{"id":172,"type":173,"label":174,"file":137,"line":175},{"id":177,"type":178,"label":179,"file":137,"line":180,"wp_function":181},[193],{"from":172,"to":177,"sanitized":184},{"summary":195,"deductions":196},"The 'wp-output-log-file' plugin v1.2.2 exhibits a generally strong security posture based on the provided static analysis.  The absence of any AJAX handlers, REST API routes, shortcodes, or cron events indicates a very limited attack surface, and importantly, no unprotected entry points were identified. The code also demonstrates good practices with 100% of SQL queries utilizing prepared statements and a high percentage of output being properly escaped.  The presence of a nonce check is also a positive sign.  Furthermore, the plugin has a clean vulnerability history with zero known CVEs, suggesting a history of secure development or diligent maintenance.\n\nDespite these strengths, there are minor areas for consideration. The plugin performs four file operations, which inherently carry some risk, although the taint analysis shows no unsanitized paths.  The absence of capability checks on any potential entry points, while currently not a concern due to the zero attack surface, could become a vulnerability if future updates introduce new functionalities. The limited scope of the taint analysis (only 2 flows) means it's possible that other, unanalyzed flows could exist with vulnerabilities. Overall, the plugin appears to be well-secured for its current version and functionality, with minimal identified risks.",[197,199,201],{"reason":198,"points":83},"File operations present inherent risk",{"reason":200,"points":31},"No capability checks found",{"reason":202,"points":31},"Limited taint flow analysis scope","2026-03-16T20:31:44.756Z",{"wat":205,"direct":210},{"assetPaths":206,"generatorPatterns":207,"scriptPaths":208,"versionParams":209},[],[],[],[],{"cssClasses":211,"htmlComments":212,"htmlAttributes":213,"restEndpoints":214,"jsGlobals":215,"shortcodeOutput":216},[],[],[],[],[],[]]