[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fx_rvGOouPGKlQpc7WA_HWVXAKJfVkWUGRpSXMnnIiTo":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":11,"num_ratings":11,"last_updated":13,"tested_up_to":14,"requires_at_least":15,"requires_php":16,"tags":17,"homepage":23,"download_link":24,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27,"vulnerabilities":28,"developer":29,"crawl_stats":26,"alternatives":36,"analysis":133,"fingerprints":227},"fullworks-support-diagnostics","Fullworks Support Diagnostics","1.0.0","fullworks","https:\u002F\u002Fprofiles.wordpress.org\u002Ffullworks\u002F","\u003Cp>Fullworks Support Diagnostics makes it easier for plugin developers to troubleshoot issues by automatically collecting diagnostic information and providing powerful debugging tools. It discovers installed plugins and provides a framework for plugin-specific diagnostic data collection.\u003C\u002Fp>\n\u003Cp>This plugin should only be activated when instructed by plugin support personnel for diagnostic purposes.\u003C\u002Fp>\n\u003Ch4>Key Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Automatic plugin discovery\u003C\u002Fstrong> – Detects compatible plugins with support-config.json files\u003C\u002Fli>\n\u003Cli>\u003Cstrong>System information collection\u003C\u002Fstrong> – Gathers essential WordPress environment data\u003C\u002Fli>\n\u003Cli>\u003Cstrong>wp-config.php debug management\u003C\u002Fstrong> – Safely modify debug constants with automatic backups\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Shortcode scanning\u003C\u002Fstrong> – Identifies shortcodes used across your site\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Freemius integration\u003C\u002Fstrong> – Collects license status and Freemius state for premium plugins\u003C\u002Fli>\n\u003Cli>\u003Cstrong>REST API endpoints\u003C\u002Fstrong> – Allows secure remote diagnostics with temporary access links\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Sensitive data protection\u003C\u002Fstrong> – Masks API keys and other confidential information\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Debug log monitoring\u003C\u002Fstrong> – Checks and displays the most recent log entries\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Debug Management\u003C\u002Fh4>\n\u003Cp>The plugin can safely manage debug constants in wp-config.php:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Enable\u002Fdisable WordPress debugging with a single click\u003C\u002Fli>\n\u003Cli>Automatically creates backups of wp-config.php before any modifications\u003C\u002Fli>\n\u003Cli>Clearly marks all changes with comment blocks for easy identification\u003C\u002Fli>\n\u003Cli>Safely removes all modifications when the feature is disabled\u003C\u002Fli>\n\u003Cli>Monitors debug log files for recent entries\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Security Considerations\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>All wp-config.php modifications require explicit admin confirmation\u003C\u002Fli>\n\u003Cli>Access keys can be regenerated at any time\u003C\u002Fli>\n\u003Cli>Temporary access links expire after 24 hours\u003C\u002Fli>\n\u003Cli>API keys and sensitive data are masked in diagnostic reports\u003C\u002Fli>\n\u003Cli>REST API endpoint can be disabled if not needed\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Usage Instructions\u003C\u002Fh3>\n\u003Ch4>For Site Owners\u003C\u002Fh4>\n\u003Col>\n\u003Cli>\u003Cstrong>Only install when directed by support personnel\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Go to Tools \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Plugin Support Diagnostics in your WordPress admin\u003C\u002Fli>\n\u003Cli>If instructed, enable debug management and select appropriate debug constants\u003C\u002Fli>\n\u003Cli>Click “Generate Diagnostic Data”\u003C\u002Fli>\n\u003Cli>Share the diagnostic information with support using one of these methods:\n\u003Cul>\n\u003Cli>Copy to clipboard\u003C\u002Fli>\n\u003Cli>Download as JSON\u003C\u002Fli>\n\u003Cli>Use the temporary direct access link (valid for 24 hours)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>When troubleshooting is complete, disable any debug options and consider deactivating the plugin\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>For Plugin Developers\u003C\u002Fh4>\n\u003Cp>To make your plugin compatible with Support Diagnostics, create a \u003Ccode>support-config.json\u003C\u002Fcode> file in your plugin’s root directory. See the example-support-config.json file included in the plugin for reference.\u003C\u002Fp>\n","A diagnostic tool that helps plugin developers provide better support by collecting relevant system information and managing debug constants.",0,345,"","6.8.5","5.8","7.4",[18,19,20,21,22],"debug","diagnostics","support","troubleshooting","wp-config","https:\u002F\u002Ffullworksplugins.com\u002Fproducts\u002Fsupport-diagnostics\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffullworks-support-diagnostics.1.0.0.zip",100,null,"2026-03-15T10:48:56.248Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":30,"total_installs":31,"avg_security_score":32,"avg_patch_time_days":33,"trust_score":34,"computed_at":35},13,78750,94,1372,75,"2026-04-03T19:58:39.508Z",[37,58,79,95,112],{"slug":38,"name":39,"version":40,"author":41,"author_profile":42,"description":43,"short_description":44,"active_installs":45,"downloaded":46,"rating":25,"num_ratings":47,"last_updated":48,"tested_up_to":14,"requires_at_least":49,"requires_php":50,"tags":51,"homepage":52,"download_link":53,"security_score":54,"vuln_count":55,"unpatched_count":11,"last_vuln_date":56,"fetched_at":57},"wp-debugging","WP Debugging","2.12.2","Andy Fragen","https:\u002F\u002Fprofiles.wordpress.org\u002Fafragen\u002F","\u003Cp>This plugin sets the following debug constants in \u003Ccode>wp-config.php\u003C\u002Fcode> on plugin activation and removes them on plugin deactivation. Any errors will result in a PHP Exception being thrown. Debug constants per \u003Ca href=\"https:\u002F\u002Fdeveloper.wordpress.org\u002Fadvanced-administration\u002Fdebug\u002Fdebug-wordpress\u002F\" rel=\"nofollow ugc\">Debugging in WordPress\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Default settings:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'WP_DEBUG_LOG', true );\ndefine( 'SCRIPT_DEBUG', true );\ndefine( 'SAVEQUERIES', true );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp> \u003Cbr \u002F>\n    @ini_set( ‘display_errors’, 1 ); is set when the plugin is active. \u003Ccode>WP_DEBUG\u003C\u002Fcode> is set to true when the plugin is first run, thereafter it can be turned off in the Settings.\u003C\u002Fp>\n\u003Cp>The Settings page allows the user to set the following.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'WP_DEBUG', true ); \u002F\u002F Default on initial plugin installation.\ndefine( 'WP_DEBUG_DISPLAY', false ); \u002F\u002F Default when not declared is true.\ndefine( 'WP_DISABLE_FATAL_ERROR_HANDLER', true ); \u002F\u002F WordPress 5.2 WSOD Override.\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>When the plugin is deactivated best efforts are made to re-add pre-existing constants to their former state. When the plugin is activated the default settings and any saved settings are restored.\u003C\u002Fp>\n\u003Cp>This plugin uses the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fwp-cli\u002Fwp-config-transformer\" rel=\"nofollow ugc\">wp-cli\u002Fwp-config-transformer\u003C\u002Fa> command for writing constants to \u003Ccode>wp-config.php\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fnorcross\u002Fdebug-quick-look\" rel=\"nofollow ugc\">Debug Quick Look\u003C\u002Fa> from Andrew Norcross is included with this plugin to assist in reading the debug.log file. If you already have this plugin installed you should delete it when WP Debugging is not active.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fquery-monitor\u002F\" rel=\"ugc\">Query Monitor\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdebug-bar\u002F\" rel=\"ugc\">Debug Bar\u003C\u002Fa> plugins are optional dependencies to aid in debugging and troubleshooting. The notice for installation will recur 45 days after being dismissed.\u003C\u002Fp>\n\u003Cp>If you have a non-standard location for your \u003Ccode>wp-config.php\u003C\u002Fcode> file you can use the filter \u003Ccode>wp_debugging_config_path\u003C\u002Fcode> to return the file path for your installation.\u003C\u002Fp>\n\u003Cp>The filter \u003Ccode>wp_debugging_add_constants\u003C\u002Fcode> allows the user to add constants to \u003Ccode>wp-config.php\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>The filter returns an array where the key is the name of the constant and the value is an array of data containing the value as a string and a boolean to indicate whether or not the value should be passed without quotes.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$my_constants = [\n    'my_test_constant' =>\n    [\n        'value' => 'abc123',\n        'raw' => false,\n    ],\n    'another_test_constant' => [ 'value' => 'true' ],\n];\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The \u003Ccode>value\u003C\u002Fcode> option contains the constant’s value as a string.\u003C\u002Fp>\n\u003Cp>The \u003Ccode>raw\u003C\u002Fcode> option means that instead of placing the value inside the config as a string it will become unquoted. The default is \u003Ccode>true\u003C\u002Fcode>. Set as \u003Ccode>false\u003C\u002Fcode> for non-boolean values.\u003C\u002Fp>\n\u003Cp>Example:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_filter(\n    'wp_debugging_add_constants',\n    function( $added_constants ) {\n        $my_constants = [\n            'my_test_constant'      => [\n                'value' => '124xyz',\n                'raw'   => false,\n            ],\n            'another_test_constant' => [ 'value' => 'true' ],\n        ];\n        return array_merge( $added_constants, $my_constants );\n    },\n    10,\n    1\n);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>This will create the following constants.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'MY_TEST_CONSTANT', '124xyz' );\ndefine( 'ANOTHER_TEST_CONSTANT', true );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>Development\u003C\u002Fh3>\n\u003Cp>PRs are welcome against the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fafragen\u002Fwp-debugging\" rel=\"nofollow ugc\">develop branch on GitHub\u003C\u002Fa>.\u003C\u002Fp>\n","A support\u002Ftroubleshooting plugin for WordPress.",10000,432358,19,"2024-12-02T19:42:00.000Z","5.2","5.6",[18,20,22],"https:\u002F\u002Fgithub.com\u002Fafragen\u002Fwp-debugging","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-debugging.2.12.2.zip",91,2,"2022-01-24 00:00:00","2026-03-15T15:16:48.613Z",{"slug":59,"name":60,"version":61,"author":62,"author_profile":63,"description":64,"short_description":65,"active_installs":66,"downloaded":67,"rating":25,"num_ratings":68,"last_updated":69,"tested_up_to":70,"requires_at_least":71,"requires_php":50,"tags":72,"homepage":76,"download_link":77,"security_score":78,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":57},"print-basic-facts","Print Basic Facts","1.3.1","Anthony Ledesma","https:\u002F\u002Fprofiles.wordpress.org\u002Fparanoia1906\u002F","\u003Cp>Time saving diagnostic tool valuable for any investigation.  View wp-config,  htaccess, file count and total size of the WordPress installation.\u003C\u002Fp>\n","Print Basic Facts will display valuable, time saving, information for a WordPress site. Optimize your troubleshooting efforts with this lightweight ap …",10,1508,1,"2018-05-16T20:08:00.000Z","4.9.29","4.8.3",[19,73,74,21,75],"file-count","tools","wp-config-reader","https:\u002F\u002Fgithub.com\u002Fparanoia1906\u002Fwp-pbf","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fprint-basic-facts.1.3.1.zip",85,{"slug":80,"name":81,"version":82,"author":83,"author_profile":84,"description":85,"short_description":86,"active_installs":11,"downloaded":87,"rating":11,"num_ratings":11,"last_updated":88,"tested_up_to":89,"requires_at_least":49,"requires_php":50,"tags":90,"homepage":93,"download_link":94,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":57},"debug-toggle","Debug Toggle","1.7.8","webjive","https:\u002F\u002Fprofiles.wordpress.org\u002Fwebjive\u002F","\u003Cp>\u003Cstrong>Debug Toggle\u003C\u002Fstrong> is a WordPress plugin that allows administrators to easily manage WordPress debug settings directly from the dashboard. It provides the ability to enable or disable individual debug constants, such as \u003Ccode>WP_DEBUG\u003C\u002Fcode>, \u003Ccode>WP_DEBUG_LOG\u003C\u002Fcode>, \u003Ccode>WP_DEBUG_DISPLAY\u003C\u002Fcode>, \u003Ccode>SCRIPT_DEBUG\u003C\u002Fcode>, and \u003Ccode>SAVEQUERIES\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Features:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Toggle Debug Settings Individually:\u003C\u002Fstrong> Enable or disable each debug setting according to your needs.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Debug Monitoring:\u003C\u002Fstrong> Prevent other plugins or themes from changing your debug settings by periodically enforcing your configurations.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Admin Bar Integration:\u003C\u002Fstrong> Quickly toggle all debug modes directly from the admin bar menu.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Uninstall Options:\u003C\u002Fstrong> Choose to remove all plugin data upon uninstalling the plugin, including removing debug constants from \u003Ccode>wp-config.php\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Automatic Cleanup on Reinstall:\u003C\u002Fstrong> Removes duplicate debug constants from \u003Ccode>wp-config.php\u003C\u002Fcode> on activation to ensure clean configuration.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Why Use Debug Toggle?\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Managing debug settings can be cumbersome, especially when you need to edit the \u003Ccode>wp-config.php\u003C\u002Fcode> file manually. Debug Toggle simplifies this process by providing an intuitive interface within the WordPress admin area, making it easier for developers and site administrators to control debugging options without directly editing core files.\u003C\u002Fp>\n\u003Ch3>License\u003C\u002Fh3>\n\u003Cp>This plugin is licensed under the GPLv2 or later.\u003C\u002Fp>\n\u003Ch3>Additional Info\u003C\u002Fh3>\n\u003Cp>For support and more information, please visit \u003Ca href=\"https:\u002F\u002Fwww.web-jive.com\" rel=\"nofollow ugc\">https:\u002F\u002Fwww.web-jive.com\u003C\u002Fa>.\u003C\u002Fp>\n","Manage WordPress debug settings from your dashboard. Toggle debug modes and prevent unauthorized changes.",172,"2025-12-01T20:34:00.000Z","6.6.5",[18,91,21,92],"development","wp-config-php","https:\u002F\u002Fwww.web-jive.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-toggle.1.7.8.zip",{"slug":96,"name":97,"version":98,"author":99,"author_profile":100,"description":101,"short_description":102,"active_installs":11,"downloaded":103,"rating":25,"num_ratings":68,"last_updated":104,"tested_up_to":105,"requires_at_least":106,"requires_php":107,"tags":108,"homepage":13,"download_link":111,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":57},"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",[18,109,110,21,22],"developer-tools","error-log","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdeveloper-debug-mode.1.2.5.zip",{"slug":113,"name":114,"version":115,"author":116,"author_profile":117,"description":118,"short_description":119,"active_installs":120,"downloaded":121,"rating":122,"num_ratings":123,"last_updated":124,"tested_up_to":105,"requires_at_least":125,"requires_php":126,"tags":127,"homepage":131,"download_link":132,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":57},"plugin-detective","Plugin Detective – Troubleshooting Conflicts","1.2.29","NSquared","https:\u002F\u002Fprofiles.wordpress.org\u002Fcroixhaug\u002F","\u003Cp>\u003Cstrong>Plugin Detective helps you troubleshoot issues on your site quickly and easily to find the cause of a problem.\u003C\u002Fstrong> Once the culprit is found, the problem plugin can be quickly deactivated. You can even fix your site when it has the white screen of death (fatal error). You’ll want to have Plugin Detective installed, so if your site crashes from a conflict or bad plugin update, you can get it back up and running quickly!\u003C\u002Fp>\n\u003Cp>Plugin Detective is your best friend when you need to:\u003Cbr \u002F>\n– Troubleshoot WordPress plugin conflicts\u003Cbr \u002F>\n– Remove stuck .maintenance files\u003Cbr \u002F>\n– Recover your site from fatal errors caused by plugins\u003C\u002Fp>\n\u003Cp>We’ve all been there–something’s broken on your site. You’ve looked around the web for advice about what to do and have stumbled across the typical wisdom: deactivate all your plugins and then reactivate them one by one, checking your site for the problem after each reactivation.\u003C\u002Fp>\n\u003Cp>Ugh.\u003C\u002Fp>\n\u003Cp>Sure, it works. But who has \u003Cem>time\u003C\u002Fem> for that?\u003C\u002Fp>\n\u003Cdiv class=\"embed-vimeo\" style=\"text-align: center;\">\u003Ciframe loading=\"lazy\" src=\"https:\u002F\u002Fplayer.vimeo.com\u002Fvideo\u002F270010645\" width=\"750\" height=\"422\" frameborder=\"0\" webkitallowfullscreen mozallowfullscreen allowfullscreen>\u003C\u002Fiframe>\u003C\u002Fdiv>\n\u003Ch4>Find Plugin Conflicts with Detective Otto Bot\u003C\u002Fh4>\n\u003Cp>Detective Otto Bot walks you through solving your case one step at a time, all from one single screen.\u003C\u002Fp>\n\u003Col>\n\u003Cli>Open a case and tell Detective Otto where you’re seeing the problem. If your site requires any plugins to run correctly, tell Otto about those, too.\u003C\u002Fli>\n\u003Cli>Then, Otto will interrogate the suspects and track clues, checking in with you from time to time.\u003C\u002Fli>\n\u003Cli>All you need to do is answer “Yes, it’s fixed” or “No, it’s still broken” each time. Otto will do the rest and find the culprit in minutes.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Best of all – Plugin Detective can work even if you’re seeing the White Screen of Death on your site or if all you can see are PHP errors. Please have a look at the FAQ’s for how to access Plugin Detective and log into WordPress even if you can’t get to your login screen.\u003C\u002Fp>\n\u003Cp>Once Otto has identified the culprit, you can quickly deactivate the troublesome plugin and go about your day.\u003C\u002Fp>\n\u003Ch4>Remove Stuck .Maintenance File or Scheduled Maintenance\u003C\u002Fh4>\n\u003Cp>Have you gotten stuck in maintenance mode on WordPress? The dreaded “Briefly unavailable for scheduled maintenance. Check back in a minute” message haunts you; the minute never ends!\u003C\u002Fp>\n\u003Cp>With Plugin Detective installed you can quickly get out of these situations without the hassle of deleting files via your host or FTP. Just tack on this slug to the end of your website URL:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002Fwp-content\u002Fplugins\u002Fplugin-detective\u002Ftroubleshoot\u002F?restore=1\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>So that your URL looks like this:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>https:\u002F\u002Fyoursite.com\u002Fwp-content\u002Fplugins\u002Fplugin-detective\u002Ftroubleshoot\u002F?restore=1\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>This will prompt you to log in and automatically remove that stuck maintenance file for you.\u003C\u002Fp>\n\u003Ch4>Who Can Use This Troubleshooting Tool?\u003C\u002Fh4>\n\u003Cp>Plugin Detective is a tool that requires no coding experience or technical knowledge to use. For that reason, Plugin Detective is the ideal troubleshooting and conflict-checking tool for:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Any WordPress website owner\u003C\u002Fli>\n\u003Cli>Developers and technical support engineers\u003C\u002Fli>\n\u003Cli>Plugin and theme owners and their support teams\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Debug Tool Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Strategically activate and deactivate plugins on your site to help you find the plugin causing trouble\u003C\u002Fli>\n\u003Cli>Open Plugin Detective for troubleshooting on any page on your site – both in the backend and the frontend!\u003C\u002Fli>\n\u003Cli>Choose any subset of your active plugins as the baseline for your testing  \u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Loved by Plugin Support Teams\u003C\u002Fh4>\n\u003Cp>The \u003Ca href=\"https:\u002F\u002Fsimplyscheduleappointments.com\u002Fguides\u002Fplugin-detective-for-plugin-conflicts\u002F\" rel=\"nofollow ugc\">Simply Schedule Appointments\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fwpdrawattention.com\u002Fguides\u002Fplugin-detective-for-finding-conflicts\u002F\" rel=\"nofollow ugc\">Draw Attention\u003C\u002Fa> support teams love to share this conflict-checking tool with their customers.\u003Cbr \u002F>\nPlugin Detective makes it easy for their clients to debug performance issues and figure out plugin conflicts in a jiffy!\u003C\u002Fp>\n\u003Ch3>1.2.14 – 2023-06-10\u003C\u002Fh3>\n\u003Ch4>Features and Improvements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Fix PHP 8.2 compatibility\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>1.2.13 – 2023-05-25\u003C\u002Fh3>\n\u003Ch4>Features and Improvements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Update required WP version to 6.1\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>1.2.12 – 2023-05-25\u003C\u002Fh3>\n\u003Ch4>Features and Improvements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Update required WP version to 6.1\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>1.2.11 – 2023-04-27\u003C\u002Fh3>\n\u003Ch4>Features and Improvements\u003C\u002Fh4>\n\u003Cp>PR:#25 – Compatibility with WordPress 6.2\u003C\u002Fp>\n\u003Ch3>1.2.10 – 2023-04-11\u003C\u002Fh3>\n\u003Ch4>Fixes\u003C\u002Fh4>\n\u003Cp>PR:#19 – Prevent fatal error on WP versions where WP_Textdomain_Registry doesn…\u003C\u002Fp>\n\u003Ch4>Features and Improvements\u003C\u002Fh4>\n\u003Ch3>1.2.9 – 2023-03-28\u003C\u002Fh3>\n\u003Ch4>Fixes\u003C\u002Fh4>\n\u003Ch4>Features and Improvements\u003C\u002Fh4>\n\u003Ch3>1.2.8 – 2023-03-28\u003C\u002Fh3>\n\u003Ch4>Fixes\u003C\u002Fh4>\n\u003Ch4>Features and Improvements\u003C\u002Fh4>\n\u003Ch3>1.2.7 – 2023-03-28\u003C\u002Fh3>\n\u003Ch4>Fixes\u003C\u002Fh4>\n\u003Ch4>Features and Improvements\u003C\u002Fh4>\n\u003Ch3>1.2.6 – 2023-02-24\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>no changes\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>1.2.3\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Fixed for WP 6.1 compatibility\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>1.2.1\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Fixed for WP 5.9 compatibility\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>1.1.8\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Fixed for WP 5.8 compatibility\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>1.1.8\u003C\u002Fh3>\n\u003Cp>For older changelog entries, please see the \u003Ca href=\"https:\u002F\u002Fplugins.svn.wordpress.org\u002Fplugin-detective\u002Ftrunk\u002FCHANGELOG.md\" rel=\"nofollow ugc\">additional changelog.txt file\u003C\u002Fa> delivered with the plugin.\u003C\u002Fp>\n","Plugin Detective helps you troubleshoot issues on your site quickly and easily to find the cause of a problem. Once the culprit is found, the problem  …",5000,211383,80,48,"2025-12-09T17:11:00.000Z","6.1","5.3",[128,129,18,20,130],"administration","conflicts","troubleshoot","https:\u002F\u002Fnsquared.io","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fplugin-detective.1.2.29.zip",{"attackSurface":134,"codeSignals":187,"taintFlows":218,"riskAssessment":219,"analyzedAt":226},{"hooks":135,"ajaxHandlers":164,"restRoutes":174,"shortcodes":184,"cronEvents":185,"entryPointCount":186,"unprotectedCount":55},[136,143,148,152,156,160],{"type":137,"name":138,"callback":139,"priority":140,"file":141,"line":142},"action","plugins_loaded","wpsa_initialize_plugin",5,"fullworks-support-diagnostics.php",55,{"type":137,"name":144,"callback":145,"file":146,"line":147},"admin_notices","closure","src\\Core\\Main.php",103,{"type":137,"name":149,"callback":150,"file":146,"line":151},"admin_menu","add_admin_menu",152,{"type":137,"name":153,"callback":154,"file":146,"line":155},"admin_init","register_settings",153,{"type":137,"name":157,"callback":158,"file":146,"line":159},"admin_enqueue_scripts","enqueue_admin_scripts",154,{"type":137,"name":161,"callback":162,"file":146,"line":163},"rest_api_init","register_rest_route",157,[165,170],{"action":166,"nopriv":167,"callback":168,"hasNonce":167,"hasCapCheck":167,"file":146,"line":169},"fwpsd_generate_diagnostic_data",false,"ajax_generate_diagnostic_data",160,{"action":171,"nopriv":167,"callback":172,"hasNonce":167,"hasCapCheck":167,"file":146,"line":173},"fwpsd_regenerate_keys","ajax_regenerate_keys",161,[175],{"namespace":176,"route":177,"methods":178,"callback":180,"permissionCallback":181,"file":182,"line":183},"fullworks-support-diagnostics\u002Fv1","\u002Fdiagnostics",[179],"GET","rest_api_callback","rest_api_permission_check","src\\REST\\DiagnosticsEndpoint.php",28,[],[],3,{"dangerousFunctions":188,"sqlUsage":189,"outputEscaping":192,"fileOperations":68,"externalRequests":11,"nonceChecks":186,"capabilityChecks":216,"bundledLibraries":217},[],{"prepared":190,"raw":11,"locations":191},6,[],{"escaped":193,"rawEcho":194,"locations":195},44,9,[196,200,202,204,206,208,210,212,214],{"file":197,"line":198,"context":199},"src\\Admin\\AdminPage.php",377,"raw output",{"file":197,"line":201,"context":199},378,{"file":197,"line":203,"context":199},389,{"file":197,"line":205,"context":199},438,{"file":197,"line":207,"context":199},440,{"file":197,"line":209,"context":199},444,{"file":197,"line":211,"context":199},450,{"file":146,"line":213,"context":199},114,{"file":146,"line":215,"context":199},117,4,[],[],{"summary":220,"deductions":221},"The \"fullworks-support-diagnostics\" v1.0.0 plugin exhibits a mixed security posture. On the positive side, it demonstrates good practices by utilizing prepared statements for all its SQL queries, performing a high percentage of output escaping, and including nonce and capability checks. The absence of dangerous functions, external HTTP requests, and a history of known vulnerabilities suggests a level of diligence in its development. However, there are significant concerns regarding its attack surface.  With 3 total entry points, 2 of which are unprotected AJAX handlers, this plugin presents a clear risk of unauthorized execution. The lack of authentication checks on these AJAX handlers is a critical oversight that could allow unauthenticated users to trigger potentially harmful actions. Taint analysis showing no flows with unsanitized paths is reassuring, but it does not mitigate the immediate risk posed by the unprotected AJAX endpoints. Overall, while the plugin has strengths in secure coding practices for database interactions and output handling, the unprotected entry points are a substantial security weakness that needs immediate attention.",[222,224],{"reason":223,"points":66},"Unprotected AJAX handlers",{"reason":225,"points":140},"Large attack surface without auth","2026-03-17T06:06:36.410Z",{"wat":228,"direct":238},{"assetPaths":229,"generatorPatterns":232,"scriptPaths":233,"versionParams":235},[230,231],"\u002Fwp-content\u002Fplugins\u002Ffullworks-support-diagnostics\u002Fassets\u002Fcss\u002Fsupport-diagnostics.css","\u002Fwp-content\u002Fplugins\u002Ffullworks-support-diagnostics\u002Fassets\u002Fjs\u002Fsupport-diagnostics.js",[],[234],"\u002Fwp-content\u002Fplugins\u002Ffullworks-support-diagnostics\u002Fvendor\u002Fautoload.php",[236,237],"fullworks-support-diagnostics\u002Fassets\u002Fcss\u002Fsupport-diagnostics.css?ver=","fullworks-support-diagnostics\u002Fassets\u002Fjs\u002Fsupport-diagnostics.js?ver=",{"cssClasses":239,"htmlComments":242,"htmlAttributes":243,"restEndpoints":245,"jsGlobals":246,"shortcodeOutput":248},[240,241],"fwpsd-debug-constants-management","fwpsd-admin-page",[],[244],"data-fwpsd-plugin-version",[],[247],"fullworks_support_diagnostics",[249,250],"[fullworks_support_diagnostics]","[fullworks_support_diagnostics_data]"]