[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fVOlffKjMY9eawIYMhT1tBrtQDcwh4IBZ4twg01cImaI":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":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":17,"tags":18,"homepage":24,"download_link":25,"security_score":26,"vuln_count":27,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30,"vulnerabilities":31,"developer":48,"crawl_stats":37,"alternatives":55,"analysis":142,"fingerprints":358},"debug-log-config-tool","Debug Log – Manager Tool","2.0.1","Lukman Nakib","https:\u002F\u002Fprofiles.wordpress.org\u002Fpyrobd\u002F","\u003Cp>A comprehensive debugging toolkit for WordPress developers and site administrators. This plugin gives you complete control over WordPress debugging without editing wp-config.php files or using FTP.\u003C\u002Fp>\n\u003Ch4>Quick Demo\u003C\u002Fh4>\n\u003Cspan class=\"embed-youtube\" style=\"text-align:center; display: block;\">\u003Ciframe loading=\"lazy\" class=\"youtube-player\" width=\"750\" height=\"422\" src=\"https:\u002F\u002Fwww.youtube.com\u002Fembed\u002FD4K5zsLnILw?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\">\u003C\u002Fiframe>\u003C\u002Fspan>\n\u003Ch4>Key Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>WP-CLI Style Terminal\u003C\u002Fstrong>: Execute WordPress commands directly from your browser with syntax highlighting and auto-completion\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Database Tools\u003C\u002Fstrong>: Run SQL queries, view table structures, and optimize your database (super admin only)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Debug Constants Manager\u003C\u002Fstrong>: Toggle all WordPress debug constants with a single click\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Log Viewer\u003C\u002Fstrong>: View, filter, and analyze debug logs with syntax highlighting and error categorization\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Query Inspector\u003C\u002Fstrong>: Examine database queries with SAVEQUERIES support\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Email Notifications\u003C\u002Fstrong>: Get alerts when new errors appear in your logs\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Safe Mode\u003C\u002Fstrong>: Quickly disable all plugins except selected ones for troubleshooting\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Custom Log Paths\u003C\u002Fstrong>: Set custom log file locations with filter support\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Debug Constants Available\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>WP_DEBUG\u003C\u002Fstrong> – Default Value: true – Enables WordPress debug mode\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WP_DEBUG_LOG\u003C\u002Fstrong> – Default Value: true – Saves all errors to a debug.log file\u003C\u002Fli>\n\u003Cli>\u003Cstrong>SCRIPT_DEBUG\u003C\u002Fstrong> – Default Value: false – Uses development versions of core JS and CSS files\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WP_DEBUG_DISPLAY\u003C\u002Fstrong> – Default Value: false – Controls whether debug messages display on screen\u003C\u002Fli>\n\u003Cli>\u003Cstrong>SAVEQUERIES\u003C\u002Fstrong> – Default Value: false – Saves database queries for analysis\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Developer Tools\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Terminal Commands\u003C\u002Fstrong>: Use WP-CLI style commands like \u003Ccode>wp core version\u003C\u002Fcode> or \u003Ccode>wp plugin list\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Database Explorer\u003C\u002Fstrong>: Run SELECT queries and view results in a formatted table\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Stack Trace Analysis\u003C\u002Fstrong>: Visualize error stack traces for easier debugging\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Hook Inspector\u003C\u002Fstrong>: View all registered hooks and their callbacks\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Environment Detection\u003C\u002Fstrong>: Development features are automatically hidden in production\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cblockquote>\n\u003Cp>\u003Cstrong>Developer API\u003C\u002Fstrong>: Apply custom filters like \u003Ccode>apply_filters('wp_debuglog_log_file_path', $file);\u003C\u002Fcode> to extend functionality\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>Please note: Constant values will be restored on plugin deactivation as it was before activating the plugin.\u003C\u002Fp>\n","The \"Debug Log Config Tool\" simplifies debugging. Toggle logging,queries , view levels, clear logs from dashboard.",3000,56110,100,21,"2025-04-30T19:04:00.000Z","6.8.5","5.6",[19,20,21,22,23],"debug","developer","log","remote-debug","tools","https:\u002F\u002Fnkb-bd.github.io\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-log-config-tool.2.0.1.zip",99,1,0,"2024-05-20 00:00:00","2026-03-15T15:16:48.613Z",[32],{"id":33,"url_slug":34,"title":35,"description":36,"plugin_slug":4,"theme_slug":37,"affected_versions":38,"patched_in_version":39,"severity":40,"cvss_score":41,"cvss_vector":42,"vuln_type":43,"published_date":29,"updated_date":44,"references":45,"days_to_patch":47},"CVE-2024-34798","debug-log-manger-tool-unauthenticated-information-exposure-via-logs","Debug Log – Manger Tool \u003C= 1.4.5 - Unauthenticated Information Exposure via Logs","The Debug Log – Manger Tool plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.4.5 through publicly exposed log files. This makes it possible for unauthenticated attackers to view potentially sensitive information contained in the exposed log files.",null,"\u003C=1.4.5","1.5","medium",5.3,"CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:L\u002FI:N\u002FA:N","Insertion of Sensitive Information into Log File","2024-05-29 20:07:01",[46],"https:\u002F\u002Fwww.wordfence.com\u002Fthreat-intel\u002Fvulnerabilities\u002Fid\u002F44c74d97-47e1-4af7-83d1-7c0e98fdc40c?source=api-prod",10,{"slug":49,"display_name":7,"profile_url":8,"plugin_count":50,"total_installs":51,"avg_security_score":52,"avg_patch_time_days":47,"trust_score":53,"computed_at":54},"pyrobd",3,3800,97,92,"2026-04-04T05:03:56.704Z",[56,75,92,109,122],{"slug":57,"name":58,"version":59,"author":60,"author_profile":61,"description":62,"short_description":63,"active_installs":47,"downloaded":64,"rating":28,"num_ratings":28,"last_updated":65,"tested_up_to":16,"requires_at_least":66,"requires_php":67,"tags":68,"homepage":73,"download_link":74,"security_score":13,"vuln_count":28,"unpatched_count":28,"last_vuln_date":37,"fetched_at":30},"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.",495,"2025-07-06T14:41:00.000Z","5.8","7.4",[69,70,71,72],"debugging","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",{"slug":76,"name":77,"version":78,"author":79,"author_profile":80,"description":81,"short_description":82,"active_installs":28,"downloaded":83,"rating":28,"num_ratings":28,"last_updated":84,"tested_up_to":16,"requires_at_least":85,"requires_php":86,"tags":87,"homepage":89,"download_link":90,"security_score":13,"vuln_count":28,"unpatched_count":28,"last_vuln_date":37,"fetched_at":91},"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,69,70,88,71],"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","2026-03-15T10:48:56.248Z",{"slug":93,"name":94,"version":95,"author":96,"author_profile":97,"description":98,"short_description":99,"active_installs":28,"downloaded":100,"rating":13,"num_ratings":27,"last_updated":101,"tested_up_to":102,"requires_at_least":103,"requires_php":104,"tags":105,"homepage":84,"download_link":108,"security_score":13,"vuln_count":28,"unpatched_count":28,"last_vuln_date":37,"fetched_at":30},"developer-debug-mode","Developer Debug Mode","1.2.5","Glimbyte","https:\u002F\u002Fprofiles.wordpress.org\u002Fglimbyte\u002F","\u003Cp>\u003Cstrong>Stop editing wp-config.php every time you need to debug your WordPress site.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Developer Debug Mode lets you toggle all WordPress debug constants directly from your dashboard with beautiful toggle switches. Changes save automatically — no clicking save buttons, no FTP access needed, no risk of syntax errors in your config file.\u003C\u002Fp>\n\u003Ch4>🎯 The Problem This Plugin Solves\u003C\u002Fh4>\n\u003Cp>Every WordPress developer knows the pain:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Something breaks on your site\u003C\u002Fli>\n\u003Cli>You need to enable WP_DEBUG to see the error\u003C\u002Fli>\n\u003Cli>You open FTP\u002FFile Manager, find wp-config.php, edit it carefully\u003C\u002Fli>\n\u003Cli>Debug the issue\u003C\u002Fli>\n\u003Cli>Remember to turn debug off before visitors see ugly error messages\u003C\u002Fli>\n\u003Cli>Repeat next time something breaks\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>\u003Cstrong>Developer Debug Mode eliminates steps 2-5 entirely.\u003C\u002Fstrong> Toggle debug on, find the error, toggle off. Done in seconds.\u003C\u002Fp>\n\u003Ch4>✨ Key Features\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>One-Click Debug Toggles\u003C\u002Fstrong>\u003Cbr \u002F>\nControl all six WordPress debug constants from a clean, modern interface:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>WP_DEBUG\u003C\u002Fstrong> — Master switch for WordPress debugging\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WP_DEBUG_LOG\u003C\u002Fstrong> — Save errors to wp-content\u002Fdebug.log\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WP_DEBUG_DISPLAY\u003C\u002Fstrong> — Show errors on screen (careful on production!)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>SCRIPT_DEBUG\u003C\u002Fstrong> — Use unminified core CSS\u002FJS files\u003C\u002Fli>\n\u003Cli>\u003Cstrong>SAVEQUERIES\u003C\u002Fstrong> — Log database queries for performance analysis\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WP_DISABLE_FATAL_ERROR_HANDLER\u003C\u002Fstrong> — See raw PHP fatal errors instead of recovery mode\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Admin Bar Quick Toggle\u003C\u002Fstrong> \u003Cem>(New in 1.2.0!)\u003C\u002Fem>\u003Cbr \u002F>\nToggle any debug constant directly from the WordPress admin bar — no need to visit the settings page. Perfect for quick debugging sessions.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Built-in Debug Log Viewer\u003C\u002Fstrong>\u003Cbr \u002F>\nView, search, download, and clear your debug.log without leaving WordPress:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Color-coded entries (fatal, error, warning, notice)\u003C\u002Fli>\n\u003Cli>Search with highlighting\u003C\u002Fli>\n\u003Cli>Auto-refresh option for real-time monitoring\u003C\u002Fli>\n\u003Cli>One-click download and clear\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Auto-Save Technology\u003C\u002Fstrong>\u003Cbr \u002F>\nChanges save instantly as you toggle. No save button, no page refresh, no waiting.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Frontend Debug Warning\u003C\u002Fstrong>\u003Cbr \u002F>\nA tasteful notification bar appears when WP_DEBUG_DISPLAY is active, reminding you to turn it off before visitors see error messages.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Cross-Tab Synchronization\u003C\u002Fstrong>\u003Cbr \u002F>\nToggle debug in one browser tab and watch other open tabs update instantly.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Automatic Backups\u003C\u002Fstrong>\u003Cbr \u002F>\nEvery change creates a backup of wp-config.php. The plugin keeps the 5 most recent backups, so you can always recover if something goes wrong.\u003C\u002Fp>\n\u003Ch4>🔧 Perfect For\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Theme developers\u003C\u002Fstrong> debugging template issues\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Plugin developers\u003C\u002Fstrong> testing new code\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Site administrators\u003C\u002Fstrong> troubleshooting problems\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Agencies\u003C\u002Fstrong> managing multiple client sites\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Freelancers\u003C\u002Fstrong> who need quick debugging without FTP access\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Anyone\u003C\u002Fstrong> tired of manually editing wp-config.php\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>💡 Why Choose Developer Debug Mode?\u003C\u002Fh4>\n\u003Cp>Unlike other debug plugins, we focus on \u003Cstrong>user experience\u003C\u002Fstrong>:\u003C\u002Fp>\n\u003Cp>✅ \u003Cstrong>Instant toggles\u003C\u002Fstrong> — No save buttons, changes apply immediately\u003Cbr \u002F>\n✅ \u003Cstrong>Visual feedback\u003C\u002Fstrong> — Clear status indicators show exactly what’s enabled\u003Cbr \u002F>\n✅ \u003Cstrong>Admin bar access\u003C\u002Fstrong> — Toggle debug from anywhere in WordPress\u003Cbr \u002F>\n✅ \u003Cstrong>Production-safe\u003C\u002Fstrong> — Frontend warnings prevent accidentally exposing errors\u003Cbr \u002F>\n✅ \u003Cstrong>Modern design\u003C\u002Fstrong> — Beautiful UI that fits naturally in your dashboard\u003Cbr \u002F>\n✅ \u003Cstrong>Lightweight\u003C\u002Fstrong> — No bloat, loads only where needed\u003C\u002Fp>\n\u003Ch4>🔒 Built With Security In Mind\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Capability checks ensure only administrators can change settings\u003C\u002Fli>\n\u003Cli>Nonce verification on all AJAX requests\u003C\u002Fli>\n\u003Cli>Automatic wp-config.php backups before every change\u003C\u002Fli>\n\u003Cli>No data sent to external servers\u003C\u002Fli>\n\u003Cli>Clean uninstall removes all plugin data\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>📚 Debug Constants Explained\u003C\u002Fh4>\n\u003Cp>Not sure what each constant does? Here’s a quick guide:\u003C\u002Fp>\n\u003Cp>\u003Cstrong>WP_DEBUG\u003C\u002Fstrong>\u003Cbr \u002F>\nThe master switch. When enabled, WordPress will display PHP errors, notices, and warnings. Required for the other debug constants to work.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>WP_DEBUG_LOG\u003C\u002Fstrong>\u003Cbr \u002F>\nSaves all debug messages to \u003Ccode>\u002Fwp-content\u002Fdebug.log\u003C\u002Fcode>. Essential for debugging issues that happen in the background (AJAX, cron jobs, REST API).\u003C\u002Fp>\n\u003Cp>\u003Cstrong>WP_DEBUG_DISPLAY\u003C\u002Fstrong>\u003Cbr \u002F>\nShows errors directly on your web pages. Useful during development but \u003Cstrong>never enable on production\u003C\u002Fstrong> — it can expose sensitive information to visitors.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>SCRIPT_DEBUG\u003C\u002Fstrong>\u003Cbr \u002F>\nForces WordPress to use the development versions of core CSS and JavaScript files instead of minified versions. Helpful when debugging scripts.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>SAVEQUERIES\u003C\u002Fstrong>\u003Cbr \u002F>\nStores database queries in a global array for later analysis. Useful for identifying slow queries but adds overhead — disable when not needed.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>WP_DISABLE_FATAL_ERROR_HANDLER\u003C\u002Fstrong>\u003Cbr \u002F>\nDisables WordPress’s “recovery mode” so you see the actual PHP fatal error instead of “There has been a critical error on this website.”\u003C\u002Fp>\n\u003Ch4>🤝 Support & Documentation\u003C\u002Fh4>\n\u003Cp>Need help? We offer:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Free Support\u003C\u002Fstrong> — Post in the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fdeveloper-debug-mode\u002F\" rel=\"ugc\">WordPress.org support forum\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Documentation\u003C\u002Fstrong> — Visit \u003Ca href=\"https:\u002F\u002Fglimbyte.ie\" rel=\"nofollow ugc\">glimbyte.ie\u003C\u002Fa> for guides and tutorials\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Express Support\u003C\u002Fstrong> — Fast turnaround for urgent issues via \u003Ca href=\"https:\u002F\u002Fglimbyte.ie\u002Fsupport\" rel=\"nofollow ugc\">glimbyte.ie\u002Fsupport\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>🌐 Works Great With\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Query Monitor\u003C\u002Fstrong> — Use alongside for deeper debugging\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Debug Bar\u003C\u002Fstrong> — Compatible with Debug Bar and its add-ons\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Any caching plugin\u003C\u002Fstrong> — Clear cache after toggling debug constants\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Managed WordPress hosts\u003C\u002Fstrong> — Works on most hosts including Kinsta, WP Engine, SiteGround\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Credits\u003C\u002Fh3>\n\u003Cp>Developed with ❤️ by \u003Ca href=\"https:\u002F\u002Fglimbyte.ie\" rel=\"nofollow ugc\">Glimbyte\u003C\u002Fa> — WordPress Development & Support.\u003C\u002Fp>\n\u003Cp>Special thanks to the WordPress community for feedback and suggestions.\u003C\u002Fp>\n\u003Ch3>Privacy Policy\u003C\u002Fh3>\n\u003Cp>Developer Debug Mode does not collect, store, or transmit any personal data. All settings are stored locally in your WordPress database and wp-config.php file.\u003C\u002Fp>\n\u003Cp>The optional support contact form (available in the plugin settings) sends data directly to Glimbyte’s support team. This data is handled according to \u003Ca href=\"https:\u002F\u002Fglimbyte.ie\u002Fprivacy\" rel=\"nofollow ugc\">Glimbyte’s Privacy Policy\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Additional Info\u003C\u002Fh3>\n\u003Ch4>Contribute\u003C\u002Fh4>\n\u003Cp>Found a bug or have a feature request? We’d love to hear from you!\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Support Forum:\u003C\u002Fstrong> \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fdeveloper-debug-mode\u002F\" rel=\"ugc\">wordpress.org\u002Fsupport\u002Fplugin\u002Fdeveloper-debug-mode\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Website:\u003C\u002Fstrong> \u003Ca href=\"https:\u002F\u002Fglimbyte.ie\" rel=\"nofollow ugc\">glimbyte.ie\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Translations\u003C\u002Fh4>\n\u003Cp>Want to help translate Developer Debug Mode into your language? Visit \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Fdeveloper-debug-mode\u002F\" rel=\"nofollow ugc\">translate.wordpress.org\u003C\u002Fa> to contribute.\u003C\u002Fp>\n","Toggle WordPress debug mode instantly. No wp-config.php editing needed. Features auto-save, admin bar quick toggle, and debug log viewer.",105,"2026-02-06T13:02:00.000Z","6.9.4","5.0","7.0",[19,70,71,106,107],"troubleshooting","wp-config","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdeveloper-debug-mode.1.2.5.zip",{"slug":110,"name":111,"version":112,"author":113,"author_profile":114,"description":115,"short_description":116,"active_installs":28,"downloaded":117,"rating":13,"num_ratings":27,"last_updated":118,"tested_up_to":119,"requires_at_least":103,"requires_php":84,"tags":120,"homepage":84,"download_link":121,"security_score":53,"vuln_count":28,"unpatched_count":28,"last_vuln_date":37,"fetched_at":30},"pas-debug-log-manager","PAS Debug Log Manager","1.0.03","azeezsaleem","https:\u002F\u002Fprofiles.wordpress.org\u002Fazeezsaleem\u002F","\u003Cp>A simple WordPress plugin that allows users to view and manage the WordPress debug log. Provides options to clear the log, toggle debug logging, and display logs in a formatted view.\u003C\u002Fp>\n\u003Ch3>Short Description\u003C\u002Fh3>\n\u003Cp>A WordPress plugin to easily manage debug logs by toggling debug logging, clearing logs, and viewing logs in a formatted way.\u003C\u002Fp>\n\u003Ch3>License\u003C\u002Fh3>\n\u003Cp>This plugin is licensed under the GPLv2 or later. You are free to use, modify, and distribute this plugin as long as you adhere to the GPLv2 license.\u003C\u002Fp>\n","A simple WordPress plugin that allows users to view and manage the WordPress debug log. Provides options to clear the log, toggle debug logging, and d …",818,"2024-10-21T09:18:00.000Z","6.6.5",[19,70,71,21],"https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpas-debug-log-manager.1.0.03.zip",{"slug":123,"name":124,"version":125,"author":126,"author_profile":127,"description":128,"short_description":129,"active_installs":130,"downloaded":131,"rating":28,"num_ratings":28,"last_updated":132,"tested_up_to":133,"requires_at_least":134,"requires_php":84,"tags":135,"homepage":139,"download_link":140,"security_score":26,"vuln_count":27,"unpatched_count":28,"last_vuln_date":141,"fetched_at":30},"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",[69,20,136,137,138],"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",{"attackSurface":143,"codeSignals":210,"taintFlows":257,"riskAssessment":345,"analyzedAt":357},{"hooks":144,"ajaxHandlers":192,"restRoutes":204,"shortcodes":205,"cronEvents":206,"entryPointCount":209,"unprotectedCount":27},[145,151,155,159,162,166,170,175,180,185,189],{"type":146,"name":147,"callback":148,"file":149,"line":150},"action","admin_menu","adminMenu","app\\Classes\\DLCT_Bootstrap.php",102,{"type":146,"name":152,"callback":153,"file":149,"line":154},"wp_before_admin_bar_render","adminTopMenu",103,{"type":146,"name":156,"callback":157,"file":149,"line":158},"admin_enqueue_scripts","enqueueAdminScripts",104,{"type":146,"name":160,"callback":161,"file":149,"line":100},"wpdd_admin_page_render","showMsg",{"type":146,"name":163,"callback":164,"file":149,"line":165},"admin_init","msgDismissed",106,{"type":146,"name":167,"callback":168,"file":149,"line":169},"wp_dashboard_setup","dashboardWidget",108,{"type":171,"name":172,"callback":173,"file":149,"line":174},"filter","admin_footer_text","customFooterText",111,{"type":146,"name":176,"callback":177,"file":178,"line":179},"admin_notices","closure","app\\Controllers\\ConfigController.php",56,{"type":146,"name":181,"callback":182,"file":183,"line":184},"dlct_daily_email_check","maybeSendEmail","app\\Controllers\\NotificationController.php",12,{"type":146,"name":186,"callback":177,"priority":47,"file":187,"line":188},"init","plugin.php",29,{"type":146,"name":190,"callback":177,"file":187,"line":191},"shutdown",42,[193,199],{"action":194,"nopriv":195,"callback":196,"hasNonce":195,"hasCapCheck":195,"file":197,"line":198},"dlct_logs_admin",false,"handleRequest","app\\Classes\\AjaxHandler.php",17,{"action":200,"nopriv":195,"callback":201,"hasNonce":202,"hasCapCheck":202,"file":149,"line":203},"dlct_toggle_debug","toggleDebug",true,107,[],[],[207],{"hook":181,"callback":181,"file":183,"line":208},18,2,{"dangerousFunctions":211,"sqlUsage":224,"outputEscaping":246,"fileOperations":254,"externalRequests":28,"nonceChecks":255,"capabilityChecks":225,"bundledLibraries":256},[212,217,220],{"fn":213,"file":214,"line":215,"context":216},"shell_exec","app\\Controllers\\TerminalController.php",1667,"$timeout_exists = shell_exec('which timeout') !== null;",{"fn":213,"file":214,"line":218,"context":219},1668,"$gtimeout_exists = shell_exec('which gtimeout') !== null;",{"fn":221,"file":214,"line":222,"context":223},"proc_open",1676,"$process = proc_open($cmd_prefix . $command_string, $descriptorspec, $pipes, ABSPATH);",{"prepared":225,"raw":226,"locations":227},6,7,[228,231,233,236,239,242,244],{"file":214,"line":229,"context":230},1173,"$wpdb->get_row() with variable interpolation",{"file":214,"line":232,"context":230},1213,{"file":214,"line":234,"context":235},1321,"$wpdb->query() with variable interpolation",{"file":214,"line":237,"context":238},1362,"$wpdb->get_var() with variable interpolation",{"file":214,"line":240,"context":241},1372,"$wpdb->get_results() with variable interpolation",{"file":214,"line":243,"context":230},1391,{"file":214,"line":245,"context":241},1549,{"escaped":247,"rawEcho":209,"locations":248},23,[249,253],{"file":250,"line":251,"context":252},"app\\Classes\\DashboardWidget.php",22,"raw output",{"file":250,"line":191,"context":252},9,4,[],[258,276,284,296,304,323],{"entryPoint":259,"graph":260,"unsanitizedCount":209,"severity":275},"updateNotificationEmail (app\\Controllers\\NotificationController.php:79)",{"nodes":261,"edges":273},[262,267],{"id":263,"type":264,"label":265,"file":183,"line":266},"n0","source","$_REQUEST (x2)",82,{"id":268,"type":269,"label":270,"file":183,"line":271,"wp_function":272},"n1","sink","update_option() [Settings Manipulation]",87,"update_option",[274],{"from":263,"to":268,"sanitized":195},"low",{"entryPoint":277,"graph":278,"unsanitizedCount":209,"severity":275},"\u003CNotificationController> (app\\Controllers\\NotificationController.php:0)",{"nodes":279,"edges":282},[280,281],{"id":263,"type":264,"label":265,"file":183,"line":266},{"id":268,"type":269,"label":270,"file":183,"line":271,"wp_function":272},[283],{"from":263,"to":268,"sanitized":195},{"entryPoint":285,"graph":286,"unsanitizedCount":27,"severity":275},"update (app\\Controllers\\SafeModeController.php:40)",{"nodes":287,"edges":294},[288,292],{"id":263,"type":264,"label":289,"file":290,"line":291},"$_POST","app\\Controllers\\SafeModeController.php",45,{"id":268,"type":269,"label":270,"file":290,"line":293,"wp_function":272},46,[295],{"from":263,"to":268,"sanitized":195},{"entryPoint":297,"graph":298,"unsanitizedCount":27,"severity":275},"\u003CSafeModeController> (app\\Controllers\\SafeModeController.php:0)",{"nodes":299,"edges":302},[300,301],{"id":263,"type":264,"label":289,"file":290,"line":291},{"id":268,"type":269,"label":270,"file":290,"line":293,"wp_function":272},[303],{"from":263,"to":268,"sanitized":195},{"entryPoint":305,"graph":306,"unsanitizedCount":209,"severity":322},"executeCommand (app\\Controllers\\TerminalController.php:10)",{"nodes":307,"edges":319},[308,311,314],{"id":263,"type":264,"label":309,"file":214,"line":310},"$_POST (x2)",328,{"id":268,"type":312,"label":313,"file":214,"line":310},"transform","→ executeDatabaseQuery()",{"id":315,"type":269,"label":316,"file":214,"line":317,"wp_function":318},"n2","get_results() [SQLi]",1481,"get_results",[320,321],{"from":263,"to":268,"sanitized":195},{"from":268,"to":315,"sanitized":195},"high",{"entryPoint":324,"graph":325,"unsanitizedCount":209,"severity":322},"\u003CTerminalController> (app\\Controllers\\TerminalController.php:0)",{"nodes":326,"edges":340},[327,329,330,331,334,336,338],{"id":263,"type":264,"label":289,"file":214,"line":328},41,{"id":268,"type":269,"label":316,"file":214,"line":317,"wp_function":318},{"id":315,"type":264,"label":289,"file":214,"line":328},{"id":332,"type":269,"label":333,"file":214,"line":222,"wp_function":221},"n3","proc_open() [RCE]",{"id":335,"type":264,"label":309,"file":214,"line":310},"n4",{"id":337,"type":312,"label":313,"file":214,"line":310},"n5",{"id":339,"type":269,"label":316,"file":214,"line":317,"wp_function":318},"n6",[341,342,343,344],{"from":263,"to":268,"sanitized":202},{"from":315,"to":332,"sanitized":202},{"from":335,"to":337,"sanitized":195},{"from":337,"to":339,"sanitized":195},{"summary":346,"deductions":347},"The debug-log-config-tool plugin exhibits a mixed security posture. While it demonstrates good practices in output escaping and a relatively low number of SQL queries, significant concerns arise from its attack surface and taint analysis. The presence of an unprotected AJAX handler presents a direct entry point for attackers, further amplified by the taint analysis revealing two high-severity flows with unsanitized paths. These unsanitized paths, especially when combined with the unprotected entry point, could lead to serious vulnerabilities if user-supplied data is not properly validated and sanitized before being processed by dangerous functions like `shell_exec` or `proc_open`.\n\nThe plugin's vulnerability history, while currently showing no unpatched CVEs, does indicate a past medium-severity vulnerability related to sensitive information logging. This historical pattern, coupled with the identified code signals, suggests a potential for future security weaknesses if not addressed proactively. The presence of dangerous functions like `shell_exec` and `proc_open` alongside unsanitized input flows warrants careful review and mitigation to prevent potential command injection or other severe exploits.\n\nIn conclusion, while the plugin has strengths in output sanitization and a clean CVE record at present, the unprotected AJAX handler, high-severity taint flows, and the potential use of dangerous functions in conjunction with unsanitized data create a notable risk. The plugin's historical vulnerability also suggests a need for continued vigilance.",[348,351,353,355],{"reason":349,"points":350},"Unprotected AJAX handler",8,{"reason":352,"points":184},"2 High severity taint flows with unsanitized paths",{"reason":354,"points":47},"Use of dangerous functions (shell_exec, proc_open)",{"reason":356,"points":50},"Partial use of prepared statements for SQL","2026-03-16T18:17:39.634Z",{"wat":359,"direct":368},{"assetPaths":360,"generatorPatterns":363,"scriptPaths":364,"versionParams":365},[361,362],"\u002Fwp-content\u002Fplugins\u002Fdebug-log-config-tool\u002Fapp\u002FAssets\u002Fdist\u002Fcss\u002Fdlct-admin.css","\u002Fwp-content\u002Fplugins\u002Fdebug-log-config-tool\u002Fapp\u002FAssets\u002Fdist\u002Fjs\u002Fdlct-admin.js",[],[362],[366,367],"debug-log-config-tool\u002Fapp\u002FAssets\u002Fdist\u002Fcss\u002Fdlct-admin.css?ver=","debug-log-config-tool\u002Fapp\u002FAssets\u002Fdist\u002Fjs\u002Fdlct-admin.js?ver=",{"cssClasses":369,"htmlComments":375,"htmlAttributes":376,"restEndpoints":378,"jsGlobals":379,"shortcodeOutput":381},[370,371,372,373,374],"dlct-debug-enabled","dlct-debug-disabled","dlct-toggle-debug","dlct-loading","dlct-spinner",[],[377],"data-dlct-debug-status",[],[380],"DLCT_CONFIG",[]]