[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fVjiLgHxZH7TTeqz-DgJpmyD-GXDwxQiQ9x8aco1ywd8":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":18,"tags":19,"homepage":25,"download_link":26,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30,"vulnerabilities":31,"developer":32,"crawl_stats":29,"alternatives":38,"analysis":137,"fingerprints":305},"development-assistant","Development Assistant","1.2.10","OMG!PRESS","https:\u002F\u002Fprofiles.wordpress.org\u002Fomgpress\u002F","\u003Cp>Development Assistant is a comprehensive toolkit designed to streamline the development process and enhance support capabilities within WordPress. Whether you’re a seasoned developer or a novice WordPress user, this plugin provides essential functionalities to manage debugging, diagnose issues, and facilitate smoother development workflows.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Debugging Made Easy:\u003C\u002Fstrong> Enable WP_DEBUG, WP_DEBUG_LOG, and WP_DEBUG_DISPLAY modes directly from the WordPress admin panel without the need to manually edit the wp-config.php file. Effortlessly toggle these settings to facilitate efficient debugging and error tracking.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Create Support User in One Click:\u003C\u002Fstrong> Create a support user with a single click to provide temporary access to your WordPress environment. This feature simplifies the process of sharing debugging information with developers or support teams, enabling them to diagnose and resolve issues more effectively. You can control after how many days the user will be auto-deleted. After creating a user, you can quickly copy the credentials to the clipboard, or share them via email (optionally adding a message).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Plugin Conflict Resolution:\u003C\u002Fstrong> Simplify the process of identifying and resolving plugin conflicts. Quickly compare the performance of active and inactive plugins, and temporarily disable or enable plugins to isolate issues without disrupting your entire plugin ecosystem.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>SMTP Testing with MailHog:\u003C\u002Fstrong> Seamlessly integrate MailHog for SMTP testing purposes. Verify the functionality of email delivery within your WordPress environment, ensuring reliable communication with users and clients.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Download Plugins:\u003C\u002Fstrong> Download plugins directly from the WordPress admin panel’s plugin view. Streamline your workflow by easily obtaining plugin files for offline storage, manual installation, or testing in other environments and sandboxes. This feature facilitates seamless testing of plugins in various environments, allowing for thorough evaluation and development iterations.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Reset:\u003C\u002Fstrong> Effortlessly undo any changes made by the plugin to restore your WordPress environment to its original state. This feature deletes all plugin settings and data from the database, resets debug constants to their pre-activation states, deletes the debug.log file (if it didn’t exist before activation), and activates any temporarily deactivated plugins.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Who Can Benefit\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Power Developers:\u003C\u002Fstrong> Streamline your development workflow with a comprehensive toolkit tailored for debugging and issue resolution. Enhance productivity and efficiency while tackling complex WordPress projects.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Novice Users:\u003C\u002Fstrong> Empower yourself to diagnose and troubleshoot WordPress issues with ease. Quickly share debugging information with developers or support teams to expedite issue resolution and enhance your WordPress experience.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Development Assistant is your go-to solution for simplifying WordPress development tasks and enhancing support capabilities. Whether you’re troubleshooting intricate issues or optimizing your development workflow, this plugin equips you with the tools you need for success.\u003C\u002Fp>\n","Toolkit for debugging and customer support.",10,2056,60,2,"2025-10-08T01:06:00.000Z","6.8.5","5.0.0","7.4.0",[20,21,22,23,24],"debug","development","manager","support","testing","https:\u002F\u002Fomgpress.com\u002Fdevelopment-assistant","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdevelopment-assistant.1.2.10.zip",100,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":33,"display_name":7,"profile_url":8,"plugin_count":34,"total_installs":11,"avg_security_score":27,"avg_patch_time_days":35,"trust_score":36,"computed_at":37},"omgpress",1,30,94,"2026-04-04T00:49:36.542Z",[39,61,77,98,117],{"slug":40,"name":41,"version":42,"author":43,"author_profile":44,"description":45,"short_description":46,"active_installs":47,"downloaded":48,"rating":49,"num_ratings":50,"last_updated":51,"tested_up_to":52,"requires_at_least":53,"requires_php":54,"tags":55,"homepage":58,"download_link":59,"security_score":60,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"sf-adminbar-tools","Admin Bar Tools","4.0","Grégory Viguier","https:\u002F\u002Fprofiles.wordpress.org\u002Fgreglone\u002F","\u003Cp>The plugin adds a new tab in your admin bar with simple but useful indications and tools.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Displays the number of queries in your page and the amount of time to generate the page.\u003C\u002Fli>\n\u003Cli>Displays the php memory usage and php memory limits (constants \u003Ccode>WP_MEMORY_LIMIT\u003C\u002Fcode> and \u003Ccode>WP_MAX_MEMORY_LIMIT\u003C\u002Fcode>).\u003C\u002Fli>\n\u003Cli>displays the php version and WP version.\u003C\u002Fli>\n\u003Cli>Displays \u003Ccode>WP_DEBUG\u003C\u002Fcode>, \u003Ccode>SCRIPT_DEBUG\u003C\u002Fcode>, \u003Ccode>WP_DEBUG_LOG\u003C\u002Fcode>, \u003Ccode>WP_DEBUG_DISPLAY\u003C\u002Fcode>, and error reporting values.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>In your site front-end:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Lists the template and all template parts used in the current page (template parts added with \u003Ccode>get_template_part()\u003C\u002Fcode>). Compatible with WooCommerce’s templates.\u003C\u002Fli>\n\u003Cli>\u003Ccode>$wp_query\u003C\u002Fcode>: this will open a lightbox displaying the content of \u003Ccode>$wp_query\u003C\u002Fcode>. Click the lightbox title to reload the value, click outside the lightbox to close it.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>In your site administration:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Admin hooks: lists some oftenly used hooks (like \u003Ccode>admin_init\u003C\u002Fcode>). The indicator to the right of the line tells you how many times the hook has been triggered by a callback. A “P” means the hook has a parameter: hover it for more details. Click a hook (on its text) to auto-select its code, for example: click \u003Cem>admin_init\u003C\u002Fem> to select \u003Ccode>add_action( 'admin_init', '' );\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Ccode>$current_screen\u003C\u002Fcode>: displays the value of 4 properties of this object: \u003Ccode>id\u003C\u002Fcode>, \u003Ccode>base\u003C\u002Fcode>, \u003Ccode>parent_base\u003C\u002Fcode>, \u003Ccode>parent_file\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Ccode>$...now\u003C\u002Fcode>: displays the value of the well-known variables \u003Ccode>$pagenow\u003C\u002Fcode>, \u003Ccode>$typenow\u003C\u002Fcode>, and \u003Ccode>$taxnow\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>On a user profile page, \u003Ccode>$userdata\u003C\u002Fcode>: : this will open a lightbox displaying the user’s data.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>You can decide who’s gonna use this plugin (go to your profile page for all the settings). This way, the plugin’s items won’t show up to other users (your client for example).\u003Cbr \u002F>\nAlso, a new menu item \u003Ccode>Code Tester\u003C\u002Fcode> will appear. There you are able to do some tests with your code.\u003C\u002Fp>\n","Adds some small development tools to the admin bar.",400,15121,96,8,"2021-01-18T16:09:00.000Z","5.6.0","4.7","5.6",[20,21,56,24,57],"query","tests","https:\u002F\u002Fwww.screenfeed.fr\u002Fsf-abt\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsf-adminbar-tools.zip",85,{"slug":62,"name":63,"version":64,"author":65,"author_profile":66,"description":67,"short_description":68,"active_installs":11,"downloaded":69,"rating":28,"num_ratings":28,"last_updated":70,"tested_up_to":71,"requires_at_least":72,"requires_php":52,"tags":73,"homepage":75,"download_link":76,"security_score":60,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"back-to-the-theme","Back To The Theme","1.2.0","Mikael Korpela","https:\u002F\u002Fprofiles.wordpress.org\u002Fsimison\u002F","\u003Cp>A tool to observe how a page loads in different themes simultaneously.\u003Cbr \u002F>\nUseful for debugging plugins or Gutenberg blocks.\u003C\u002Fp>\n\u003Cp>How to Use:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Install several themes you’d like to check out.\u003C\u002Fli>\n\u003Cli>Create a new page.\u003C\u002Fli>\n\u003Cli>Navigate to \u003Cem>Tools\u003C\u002Fem> \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> \u003Cem>Back To The Theme\u003C\u002Fem>\u003C\u002Fli>\n\u003Cli>Choose if you want to demo editor- or view side.\u003C\u002Fli>\n\u003Cli>Select the themes you’d like to check out.\u003C\u002Fli>\n\u003Cli>Choose the page you just created. This page will be previewed with all the themes you’ve selected.\u003C\u002Fli>\n\u003Cli>Click \u003Cem>Do it!\u003C\u002Fem>.\u003C\u002Fli>\n\u003Cli>Scroll to see the page rendered with all the themes you selected.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>You’ll see your page load with different themes in a bunch of iframes for handy preview and debugging.\u003C\u002Fp>\n\u003Cp>A nice list of popular themes to test:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>`\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>wp theme install \\\u003Cbr \u002F>\n  astra \\\u003Cbr \u002F>\n  colormag \\\u003Cbr \u002F>\n  customizr \\\u003Cbr \u002F>\n  generatepress \\\u003Cbr \u002F>\n  hestia \\\u003Cbr \u002F>\n  hueman \\\u003Cbr \u002F>\n  oceanwp \\\u003Cbr \u002F>\n  shapely \\\u003Cbr \u002F>\n  storefront \\\u003Cbr \u002F>\n  sydney \\\u003Cbr \u002F>\n  twentyeleven \\\u003Cbr \u002F>\n  twentyfifteen \\\u003Cbr \u002F>\n  twentyfourteen \\\u003Cbr \u002F>\n  twentynineteen \\\u003Cbr \u002F>\n  twentyseventeen \\\u003Cbr \u002F>\n  twentysixteen \\\u003Cbr \u002F>\n  twentyten \\\u003Cbr \u002F>\n  twentythirteen \\\u003Cbr \u002F>\n  twentytwelve \\\u003Cbr \u002F>\n  vantage\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Cp>See docs for \u003Ca href=\"https:\u002F\u002Fdeveloper.wordpress.org\u002Fcli\u002Fcommands\u002Ftheme\u002Finstall\u002F\" rel=\"nofollow ugc\">wp theme install\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fsimison\u002Fback-to-the-theme\" rel=\"nofollow ugc\">Plugin’s source code on GitHub\u003C\u002Fa>.\u003C\u002Fp>\n","See a page with different themes all at once, just like that!",1687,"2019-03-01T22:26:00.000Z","5.1.22","4.6",[20,21,24,74],"themes","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fback-to-the-theme.zip",{"slug":78,"name":79,"version":80,"author":81,"author_profile":82,"description":83,"short_description":84,"active_installs":85,"downloaded":86,"rating":87,"num_ratings":88,"last_updated":89,"tested_up_to":90,"requires_at_least":91,"requires_php":92,"tags":93,"homepage":96,"download_link":97,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"query-monitor","Query Monitor – The developer tools panel for WordPress","3.20.2","John Blackbourn","https:\u002F\u002Fprofiles.wordpress.org\u002Fjohnbillion\u002F","\u003Cp>Query Monitor is the developer tools panel for WordPress and WooCommerce. It enables debugging of database queries, PHP errors, hooks and actions, block editor blocks, enqueued scripts and stylesheets, HTTP API calls, and more.\u003C\u002Fp>\n\u003Cp>It includes some advanced features such as debugging of Ajax calls, REST API calls, user capability checks, and full support for block themes and full site editing. It includes the ability to narrow down much of its output by plugin or theme, allowing you to quickly determine poorly performing plugins, themes, or functions.\u003C\u002Fp>\n\u003Cp>Query Monitor focuses heavily on presenting its information in a useful manner, for example by showing aggregate database queries grouped by the plugins, themes, or functions that are responsible for them. It adds an admin toolbar menu showing an overview of the current page, with complete debugging information shown in panels once you select a menu item.\u003C\u002Fp>\n\u003Cp>Query Monitor supports versions of WordPress up to three years old, and PHP version 7.4 or higher.\u003C\u002Fp>\n\u003Cp>For complete information, please see \u003Ca href=\"https:\u002F\u002Fquerymonitor.com\u002F\" rel=\"nofollow ugc\">the Query Monitor website\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Here’s an overview of what’s shown for each page load:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Database queries, including notifications for slow, duplicate, or erroneous queries. Allows filtering by query type (\u003Ccode>SELECT\u003C\u002Fcode>, \u003Ccode>UPDATE\u003C\u002Fcode>, \u003Ccode>DELETE\u003C\u002Fcode>, etc), responsible component (plugin, theme, WordPress core), and calling function, and provides separate aggregate views for each.\u003C\u002Fli>\n\u003Cli>The template filename, the complete template hierarchy, and names of all template parts that were loaded or not loaded (for block themes and classic themes).\u003C\u002Fli>\n\u003Cli>PHP errors presented nicely along with their responsible component and call stack, and a visible warning in the admin toolbar.\u003C\u002Fli>\n\u003Cli>Usage of “Doing it Wrong” or “Deprecated” functionality in the code on your site.\u003C\u002Fli>\n\u003Cli>Blocks and associated properties within post content and within full site editing (FSE).\u003C\u002Fli>\n\u003Cli>Matched rewrite rules, associated query strings, and query vars.\u003C\u002Fli>\n\u003Cli>Enqueued scripts and stylesheets, along with their dependencies, dependents, and alerts for broken dependencies.\u003C\u002Fli>\n\u003Cli>Language settings and loaded translation files (MO files and JSON files) for each text domain.\u003C\u002Fli>\n\u003Cli>HTTP API requests, with response code, responsible component, and time taken, with alerts for failed or erroneous requests.\u003C\u002Fli>\n\u003Cli>User capability checks, along with the result and any parameters passed to the capability check.\u003C\u002Fli>\n\u003Cli>Environment information, including detailed information about PHP, the database, WordPress, and the web server.\u003C\u002Fli>\n\u003Cli>The values of all WordPress conditional functions such as \u003Ccode>is_single()\u003C\u002Fcode>, \u003Ccode>is_home()\u003C\u002Fcode>, etc.\u003C\u002Fli>\n\u003Cli>Transients that were updated.\u003C\u002Fli>\n\u003Cli>Usage of \u003Ccode>switch_to_blog()\u003C\u002Fcode> and \u003Ccode>restore_current_blog()\u003C\u002Fcode> on Multisite installations.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>In addition:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Whenever a redirect occurs, Query Monitor adds an HTTP header containing the call stack, so you can use your favourite HTTP inspector or browser developer tools to trace what triggered the redirect.\u003C\u002Fli>\n\u003Cli>The response from any jQuery-initiated Ajax request on the page will contain various debugging information in its headers. PHP errors also get output to the browser’s developer console.\u003C\u002Fli>\n\u003Cli>The response from an authenticated WordPress REST API request will contain an overview of performance information and PHP errors in its headers, as long as the authenticated user has permission to view Query Monitor’s output. An \u003Ca href=\"https:\u002F\u002Fdeveloper.wordpress.org\u002Frest-api\u002Fusing-the-rest-api\u002Fglobal-parameters\u002F#_envelope\" rel=\"nofollow ugc\">an enveloped REST API request\u003C\u002Fa> will include even more debugging information in the \u003Ccode>qm\u003C\u002Fcode> property of the response.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>By default, Query Monitor’s output is only shown to Administrators on single-site installations, and Super Admins on Multisite installations.\u003C\u002Fp>\n\u003Cp>In addition to this, you can set an authentication cookie which allows you to view Query Monitor output when you’re not logged in (or if you’re logged in as a non-Administrator). See the Settings panel for details.\u003C\u002Fp>\n\u003Ch3>Other Plugins\u003C\u002Fh3>\n\u003Cp>I maintain several other plugins for developers. Check them out:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fuser-switching\u002F\" rel=\"ugc\">User Switching\u003C\u002Fa> provides instant switching between user accounts in WordPress.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-crontrol\u002F\" rel=\"ugc\">WP Crontrol\u003C\u002Fa> lets you view and control what’s happening in the WP-Cron system\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Privacy Statement\u003C\u002Fh3>\n\u003Cp>Query Monitor is private by default and always will be. It does not persistently store any of the data that it collects. It does not send data to any third party, nor does it include any third party resources. \u003Ca href=\"https:\u002F\u002Fquerymonitor.com\u002Fprivacy\u002F\" rel=\"nofollow ugc\">Query Monitor’s full privacy statement can be found here\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Accessibility Statement\u003C\u002Fh3>\n\u003Cp>Query Monitor aims to be fully accessible to all of its users. \u003Ca href=\"https:\u002F\u002Fquerymonitor.com\u002Faccessibility\u002F\" rel=\"nofollow ugc\">Query Monitor’s full accessibility statement can be found here\u003C\u002Fa>.\u003C\u002Fp>\n","Query Monitor is the developer tools panel for WordPress and WooCommerce.",200000,19156533,98,463,"2025-12-11T22:16:00.000Z","6.9.4","6.1","7.4",[20,94,21,95,78],"debug-bar","performance","https:\u002F\u002Fquerymonitor.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fquery-monitor.3.20.2.zip",{"slug":99,"name":100,"version":101,"author":102,"author_profile":103,"description":104,"short_description":105,"active_installs":106,"downloaded":107,"rating":27,"num_ratings":108,"last_updated":109,"tested_up_to":16,"requires_at_least":110,"requires_php":54,"tags":111,"homepage":113,"download_link":114,"security_score":115,"vuln_count":14,"unpatched_count":28,"last_vuln_date":116,"fetched_at":30},"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",[20,23,112],"wp-config","https:\u002F\u002Fgithub.com\u002Fafragen\u002Fwp-debugging","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-debugging.2.12.2.zip",91,"2022-01-24 00:00:00",{"slug":118,"name":119,"version":120,"author":121,"author_profile":122,"description":123,"short_description":124,"active_installs":125,"downloaded":126,"rating":127,"num_ratings":128,"last_updated":129,"tested_up_to":90,"requires_at_least":91,"requires_php":130,"tags":131,"homepage":135,"download_link":136,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"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","5.3",[132,133,20,23,134],"administration","conflicts","troubleshoot","https:\u002F\u002Fnsquared.io","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fplugin-detective.1.2.29.zip",{"attackSurface":138,"codeSignals":204,"taintFlows":289,"riskAssessment":290,"analyzedAt":304},{"hooks":139,"ajaxHandlers":200,"restRoutes":201,"shortcodes":202,"cronEvents":203,"entryPointCount":28,"unprotectedCount":28},[140,146,149,152,156,160,164,167,170,173,176,178,181,184,188,192,194,198],{"type":141,"name":142,"callback":143,"priority":34,"file":144,"line":145},"action","admin_init","anonymous","inc\\Assistant.php",35,{"type":141,"name":147,"callback":143,"file":144,"line":148},"admin_enqueue_scripts",70,{"type":141,"name":150,"callback":143,"file":144,"line":151},"admin_notices",71,{"type":141,"name":153,"callback":143,"file":154,"line":155},"phpmailer_init","inc\\MailHog.php",26,{"type":141,"name":157,"callback":143,"file":158,"line":159},"activate_plugin","inc\\PluginsScreen\\ActivationManager.php",31,{"type":161,"name":162,"callback":143,"file":158,"line":163},"filter","bulk_actions-plugins",32,{"type":161,"name":165,"callback":143,"priority":11,"file":158,"line":166},"handle_bulk_actions-plugins",33,{"type":141,"name":168,"callback":143,"file":169,"line":163},"admin_head-plugins.php","inc\\PluginsScreen.php",{"type":161,"name":171,"callback":143,"file":169,"line":172},"manage_plugins_columns",37,{"type":141,"name":174,"callback":143,"priority":11,"file":169,"line":175},"manage_plugins_custom_column",38,{"type":141,"name":147,"callback":143,"file":169,"line":177},39,{"type":141,"name":142,"callback":143,"file":179,"line":180},"inc\\Setting\\BasePage.php",21,{"type":141,"name":182,"callback":143,"file":179,"line":183},"updated_option",22,{"type":141,"name":185,"callback":143,"file":186,"line":187},"admin_head","inc\\Setting\\DebugLog.php",34,{"type":141,"name":189,"callback":143,"file":190,"line":191},"admin_menu","inc\\Setting\\Page.php",17,{"type":141,"name":147,"callback":143,"file":190,"line":193},18,{"type":141,"name":195,"callback":143,"file":196,"line":197},"deleted_user","inc\\Setting\\SupportUser.php",61,{"type":141,"name":142,"callback":143,"file":196,"line":199},74,[],[],[],[],{"dangerousFunctions":205,"sqlUsage":206,"outputEscaping":208,"fileOperations":286,"externalRequests":34,"nonceChecks":34,"capabilityChecks":287,"bundledLibraries":288},[],{"prepared":28,"raw":28,"locations":207},[],{"escaped":209,"rawEcho":177,"locations":210},154,[211,214,216,218,221,222,224,225,227,230,231,233,235,237,239,240,242,244,245,247,249,251,253,255,257,259,261,263,265,267,269,271,273,275,277,279,280,282,284],{"file":169,"line":212,"context":213},83,"raw output",{"file":169,"line":215,"context":213},89,{"file":169,"line":217,"context":213},97,{"file":219,"line":220,"context":213},"inc\\Setting\\Control.php",122,{"file":186,"line":199,"context":213},{"file":186,"line":223,"context":213},81,{"file":186,"line":27,"context":213},{"file":186,"line":226,"context":213},138,{"file":228,"line":229,"context":213},"inc\\Setting\\DevEnv.php",101,{"file":228,"line":229,"context":213},{"file":228,"line":232,"context":213},103,{"file":196,"line":234,"context":213},162,{"file":196,"line":236,"context":213},165,{"file":196,"line":238,"context":213},174,{"file":196,"line":238,"context":213},{"file":196,"line":241,"context":213},176,{"file":196,"line":243,"context":213},180,{"file":196,"line":243,"context":213},{"file":196,"line":246,"context":213},188,{"file":196,"line":248,"context":213},192,{"file":196,"line":250,"context":213},201,{"file":196,"line":252,"context":213},229,{"file":196,"line":254,"context":213},230,{"file":196,"line":256,"context":213},236,{"file":196,"line":258,"context":213},237,{"file":196,"line":260,"context":213},244,{"file":196,"line":262,"context":213},245,{"file":196,"line":264,"context":213},249,{"file":196,"line":266,"context":213},269,{"file":196,"line":268,"context":213},277,{"file":196,"line":270,"context":213},279,{"file":196,"line":272,"context":213},304,{"file":196,"line":274,"context":213},309,{"file":196,"line":276,"context":213},425,{"file":196,"line":278,"context":213},433,{"file":196,"line":278,"context":213},{"file":196,"line":281,"context":213},438,{"file":196,"line":283,"context":213},440,{"file":196,"line":285,"context":213},443,4,11,[],[],{"summary":291,"deductions":292},"The \"development-assistant\" plugin v1.2.10 exhibits a generally strong security posture based on the provided static analysis.  The complete absence of AJAX handlers, REST API routes, shortcodes, and cron events with unprotected entry points is a significant strength, greatly reducing the plugin's attack surface.  The code also demonstrates good practices regarding SQL queries, exclusively using prepared statements, and a high percentage of output escaping.  Furthermore, the plugin has no recorded vulnerabilities, including CVEs, which is highly positive.\n\nHowever, there are minor areas for attention. The plugin performs file operations and makes external HTTP requests, which inherently introduce potential risks if not handled with extreme care. While the analysis shows a nonce check and a capability check, the limited number of these checks for the 193 outputs and file operations could be a concern if sensitive data is being processed or displayed. The taint analysis showing zero flows might indicate a lack of complex data flow analysis or that the plugin genuinely has no exploitable data flows, but it's difficult to be certain without more context on the analysis depth.\n\nOverall, the plugin appears to be developed with security in mind, prioritizing a small attack surface and secure data handling.  The lack of historical vulnerabilities further reinforces this.  The primary recommendations would be to ensure that all file operations and external HTTP requests are rigorously secured and that the limited checks are sufficient for the potential sensitivity of the data involved. The limited taint analysis is a minor unknown but doesn't currently present an actionable risk.",[293,296,298,300,302],{"reason":294,"points":295},"Unescaped output exists (20% of 193)",6,{"reason":297,"points":14},"File operations present",{"reason":299,"points":14},"External HTTP requests present",{"reason":301,"points":14},"Limited number of capability checks",{"reason":303,"points":14},"Limited number of nonce checks","2026-03-16T23:45:49.460Z",{"wat":306,"direct":315},{"assetPaths":307,"generatorPatterns":310,"scriptPaths":311,"versionParams":312},[308,309],"\u002Fwp-content\u002Fplugins\u002Fdevelopment-assistant\u002Fbuild\u002Fcss\u002Fapp.css","\u002Fwp-content\u002Fplugins\u002Fdevelopment-assistant\u002Fbuild\u002Fjs\u002Fapp.js",[],[309],[313,314],"development-assistant\u002Fbuild\u002Fcss\u002Fapp.css?ver=","development-assistant\u002Fbuild\u002Fjs\u002Fapp.js?ver=",{"cssClasses":316,"htmlComments":318,"htmlAttributes":319,"restEndpoints":321,"jsGlobals":325,"shortcodeOutput":328},[317],"wp-dev-assist-notice",[],[320],"data-wp-dev-assist-id",[322,323,324],"\u002Fwp-json\u002Fwp-dev-assist\u002Fv1\u002Flog","\u002Fwp-json\u002Fwp-dev-assist\u002Fv1\u002Foptions","\u002Fwp-json\u002Fwp-dev-assist\u002Fv1\u002Frequest-data",[326,327],"wpDevAssist","WPDevAssist",[]]