[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fqow5UQAYw4DAXeBvsIycVo26vu1bfr8uy5gj_3u8uS0":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":39,"analysis":141,"fingerprints":275},"query-monitor-extension-checking-variables","Checking Variables (Dev. Tool)","4.0.0","sujin2f","https:\u002F\u002Fprofiles.wordpress.org\u002Fsujin2f\u002F","\u003Cp>Are you a WordPress Developer? Just simply check the values of your variables. You can use it either in \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fquery-monitor\u002F\" rel=\"ugc\">Query Monitor\u003C\u002Fa> result and independently.\u003C\u002Fp>\n\u003Ch4>Usage\u003C\u002Fh4>\n\u003Col>\n\u003Cli>Using console( $var [, $var [, $var]] … ); function, you can check what the variable contains.\u003C\u002Fli>\n\u003Cli>You can check it on the Query Monitor – Variable Checking or your wp_footer.\u003C\u002Fli>\n\u003C\u002Fol>\n","Developers! Check your variables.",10,3104,80,1,"2015-12-22T19:04:00.000Z","4.4.34","4.2.2","",[20,21,22,23,24],"debug","develop","monitor","php","query","http:\u002F\u002Fwww.sujinc.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fquery-monitor-extension-checking-variables.4.0.0.zip",85,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":33,"total_installs":34,"avg_security_score":35,"avg_patch_time_days":36,"trust_score":37,"computed_at":38},5,140,88,30,86,"2026-04-04T19:11:07.149Z",[40,64,83,103,122],{"slug":41,"name":42,"version":43,"author":44,"author_profile":45,"description":46,"short_description":47,"active_installs":48,"downloaded":49,"rating":50,"num_ratings":51,"last_updated":52,"tested_up_to":53,"requires_at_least":54,"requires_php":55,"tags":56,"homepage":60,"download_link":61,"security_score":62,"vuln_count":14,"unpatched_count":28,"last_vuln_date":63,"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,57,58,59,41],"debug-bar","development","performance","https:\u002F\u002Fquerymonitor.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fquery-monitor.3.20.2.zip",97,"2026-03-30 23:21:22",{"slug":65,"name":66,"version":67,"author":68,"author_profile":69,"description":70,"short_description":71,"active_installs":72,"downloaded":73,"rating":72,"num_ratings":33,"last_updated":74,"tested_up_to":75,"requires_at_least":76,"requires_php":55,"tags":77,"homepage":81,"download_link":82,"security_score":72,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"debugpress","DebugPress: Debugger in Popup","4.1","Milan Petrovic","https:\u002F\u002Fprofiles.wordpress.org\u002Fgdragon\u002F","\u003Cp>DebugPress is an easy-to-use plugin implementing popup for debugging and profiling currently loaded WordPress powered website page with support for intercepting AJAX requests. The main debugger window is displayed as a popup, activated through the button with the Bug integrated into WordPress Toolbar, or floating on the page.\u003C\u002Fp>\n\u003Cp>The plugin currently has a total of 22 tabs in the popup debugger window, showing all kinds of information relevant to the current page, WordPress setup, background AJAX calls, and much more.\u003C\u002Fp>\n\u003Cp>The plugin doesn’t modify or replace any WordPress files or functions.\u003C\u002Fp>\n\u003Ch4>Home and GitHub\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Learn more about the plugin: \u003Ca href=\"https:\u002F\u002Fwww.dev4press.com\u002Fplugins\u002Fdebugpress\u002F\" rel=\"nofollow ugc\">DebugPress Website\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Contribute to plugin development: \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdev4press\u002Fdebugpress\" rel=\"nofollow ugc\">DebugPress on GitHub\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Quick Overview Video\u003C\u002Fh4>\n\u003Cp>\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\u002F-eFnBRLhy-s?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>\u003C\u002Fp>\n\u003Ch4>Pretty Print for objects\u003C\u002Fh4>\n\u003Cp>To display the content of objects or arrays, plugin has pretty print functionality through use of simpler PrettyPrint library, or more robust third-party library Kint. You can choose one or the other from the plugin Settings, Advanced tab.\u003C\u002Fp>\n\u003Ch4>Debugger Panels\u003C\u002Fh4>\n\u003Cp>Currently, the plugin has the following panels:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Basic\u003C\u002Fli>\n\u003Cli>Request (optional)\u003C\u002Fli>\n\u003Cli>Query (for frontend only)\u003C\u002Fli>\n\u003Cli>Content (optional)\u003C\u002Fli>\n\u003Cli>Roles (optional)\u003C\u002Fli>\n\u003Cli>Constants (optional)\u003C\u002Fli>\n\u003Cli>Hooks (optional)\u003C\u002Fli>\n\u003Cli>PHP (optional)\u003C\u002Fli>\n\u003Cli>Server (optional)\u003C\u002Fli>\n\u003Cli>Enqueue (optional)\u003C\u002Fli>\n\u003Cli>SQL Queries (if SQL queries logging is enabled)\u003C\u002Fli>\n\u003Cli>User (optional, if user is logged in only)\u003C\u002Fli>\n\u003Cli>HTTP (optional, if HTTP API calls are captured)\u003C\u002Fli>\n\u003Cli>bbPress (optional, on bbPress forum pages only)\u003C\u002Fli>\n\u003Cli>Plugins (optional, if plugins store data)\u003C\u002Fli>\n\u003Cli>Errors (for all captured PHP errors)\u003C\u002Fli>\n\u003Cli>Doing It Wrong (for captured WordPress Doing It Wrong warnings)\u003C\u002Fli>\n\u003Cli>Deprecated (for captured PHP deprecated warnings)\u003C\u002Fli>\n\u003Cli>AJAX (for captured AJAX calls while page is active)\u003C\u002Fli>\n\u003Cli>Store (for any user stored objects during the page loading)\u003C\u002Fli>\n\u003Cli>Tools (internal and external tools links)\u003C\u002Fli>\n\u003Cli>Debug Log (load content on demand from WordPress ‘debug.log’)\u003C\u002Fli>\n\u003Cli>Layout (control the size, position and activation of the popup)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>SQL Queries\u003C\u002Fh4>\n\u003Cp>This panel lists all the queries WordPress has run. It allows you to order the queries by execution order or length of execution, and all queries can be filtered by the query type, database table it targets or the WordPress function that called it. Every query displays the execution time, order, caller functions stack and fully formatted SQL query that is easy to read. For some Dev4Press created plugins (and that list will grow), DebugPress can detect the source of the query and allow you to filter by the plugin calling the query.\u003C\u002Fp>\n\u003Ch4>PHP and WordPress Errors\u003C\u002Fh4>\n\u003Cp>Plugin has 3 panels dedicated to showing PHP and WordPress errors and warnings. The Plugin captures this information during the page load, and it shows full debug trace as returned by the PHP debug tracing function.\u003C\u002Fp>\n\u003Ch4>AJAX\u003C\u002Fh4>\n\u003Cp>The plugin tracks every AJAX call coming through WordPress \u003Ccode>admin-ajax.php\u003C\u002Fcode> handler, and with every response, it returns HTTP headers with AJAX request basic execution information. Right now, plugin is not returning a list of logged errors or SQL queries, because both can produce huge output that goes over the HTTP header limits. Plan is to introduce these in the future plugin versions.\u003C\u002Fp>\n\u003Ch4>Info Panels\u003C\u002Fh4>\n\u003Cp>In the administration Tools menu, plugin adds DebugPress Info page showing several panels\u003C\u002Fp>\n\u003Cul>\n\u003Cli>PHP Info: full formatted results from \u003Ccode>phpinfo()\u003C\u002Fcode> function\u003C\u002Fli>\n\u003Cli>OPCache Info: full settings and statistics for the OPCache PHP extension\u003C\u002Fli>\n\u003Cli>MySQL Variables: full MySQL settings retrieved from the database\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Plugin Settings\u003C\u002Fh4>\n\u003Cp>The plugin has various options controlling the plugin activation, button integration position, user roles that can see the debugger window, options to attempt overriding WordPress debug flags and options controlling the visibility of optional debugger panels.\u003C\u002Fp>\n\u003Ch4>Log into Database\u003C\u002Fh4>\n\u003Cp>Debugger popup is visible for the request running in the browser. But there are many requests that are happening in the background (AJAX calls, REST API calls…), and for them, you can’t see errors, call information and other stuff in the debugger. Because of that, DebugPress supports logging of various events into database with the use of ‘coreActivity’ plugin, and it is highly recommended to install and use coreActivity.\u003C\u002Fp>\n\u003Cp>Log various debug events into a database with the free plugin: \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcoreactivity\u002F\" rel=\"ugc\">coreActivity Plugin\u003C\u002Fa>, supporting over 120 events and 10 popular WordPress plugins. DebugPress related events will be logged and available for later analysis, and this includes errors, AJAX calls, and HTTP API calls.\u003C\u002Fp>\n\u003Ch4>Documentation and Support\u003C\u002Fh4>\n\u003Cp>To get help with the plugin, you can use WordPress.org support forums, or you can use Dev4Press.com support forums.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Plugin Documentation: \u003Ca href=\"https:\u002F\u002Fwww.dev4press.com\u002Fkb\u002Fproduct\u002Fdebugpress\u002F\" rel=\"nofollow ugc\">DebugPress Website\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Support Forum: \u003Ca href=\"https:\u002F\u002Fsupport.dev4press.com\u002Fforums\u002Fforum\u002Fplugins-free\u002Fdebugpress\u002F\" rel=\"nofollow ugc\">Dev4Press Support\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n","Easy-to-use plugin for debugging and profiling website loading, SQL queries analysis, help with development, bug fixing, all in configurable popup.",100,14884,"2025-09-29T18:36:00.000Z","6.8.5","5.5",[78,79,80,58,41],"ajax-monitor","debugging","dev4press","https:\u002F\u002Fwww.dev4press.com\u002Fplugins\u002Fdebugpress\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebugpress.4.1.zip",{"slug":84,"name":85,"version":86,"author":87,"author_profile":88,"description":89,"short_description":90,"active_installs":91,"downloaded":92,"rating":93,"num_ratings":94,"last_updated":95,"tested_up_to":75,"requires_at_least":96,"requires_php":97,"tags":98,"homepage":18,"download_link":102,"security_score":72,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"debug-this","Debug This","0.6.7","Razvan Aldea","https:\u002F\u002Fprofiles.wordpress.org\u002Fraldea89\u002F","\u003Cp>For admins, developers, and support staff, \u003Cstrong>Debug This\u003C\u002Fstrong> provides a ton of information about your WordPress installation, all from the front-end admin bar.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cem>The current WP_Query object\u003C\u002Fem>\u003C\u002Fli>\n\u003Cli>Blog info and options\u003C\u002Fli>\n\u003Cli>Embed providers\u003C\u002Fli>\n\u003Cli>Files in rendered HTML (CSS, images, JavaScript)\u003C\u002Fli>\n\u003Cli>Filters and actions\u003C\u002Fli>\n\u003Cli>Images sizes\u003C\u002Fli>\n\u003Cli>Globals and constants\u003C\u002Fli>\n\u003Cli>Menus\u003C\u002Fli>\n\u003Cli>Object cache stats\u003C\u002Fli>\n\u003Cli>Plugins, must-use plugins, and dropins\u003C\u002Fli>\n\u003Cli>Rewrite rules\u003C\u002Fli>\n\u003Cli>Queries\u003C\u002Fli>\n\u003Cli>PHP and server information\u003C\u002Fli>\n\u003Cli>Post attachments\u003C\u002Fli>\n\u003Cli>Post types\u003C\u002Fli>\n\u003Cli>Scripts and styles enqueued\u003C\u002Fli>\n\u003Cli>Shortcodes\u003C\u002Fli>\n\u003Cli>Sidebars and widgets\u003C\u002Fli>\n\u003Cli>Taxonomies and terms\u003C\u002Fli>\n\u003Cli>Themes\u003C\u002Fli>\n\u003Cli>Users\u003C\u002Fli>\n\u003Cli>WP cron schedules and jobs\u003C\u002Fli>\n\u003Cli>WP debug log\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Debug This\u003C\u002Fstrong> helps you save time and effort when trying to figure out what’s going on. Instead of hardcoding debug snippets or writing complex unit\u003Cbr \u002F>\ntests for small functionality, you can simply bring to the surface what you need right from the admin bar.\u003C\u002Fp>\n\u003Cp>For example, when viewing a single post, you can see:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>a list of post attachments,\u003C\u002Fli>\n\u003Cli>which menus and sidebars are being displayed,\u003C\u002Fli>\n\u003Cli>the post type, post fields, and meta data,\u003C\u002Fli>\n\u003Cli>the current query variables and query string,\u003C\u002Fli>\n\u003Cli>the rewrite rules applied,\u003C\u002Fli>\n\u003Cli>the author,\u003C\u002Fli>\n\u003Cli>the terms,\u003C\u002Fli>\n\u003Cli>and much more.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Extend\u003C\u002Fh3>\n\u003Ch4>Debug This Functions\u003C\u002Fh4>\n\u003Cp>New debug modes can be created easily:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_debug_extension(\n    $mode,\n    $menu_label,\n    $description,\n    $callback,\n    $group = 'General'\n);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Example\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_debug_extension(\n    'actions',\n    __('Actions', 'debug-this'),\n    __('$wp_actions contains all active registered actions', 'debug-this'),\n    'foo_callback',\n    'Filters And Actions'\n);\nfunction foo_callback($buffer, $template){\n    global $wp_actions;\n    $debug = print_r($wp_actions, true);\n    return $debug;\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>You can add links to the header of a debug mode page. Place this code within your debug callback function.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_debug_header_link('http:\u002F\u002Furltolink', 'Link Label');\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Extensions can be removed as well using \u003Ccode>remove_debug_extension($mode);\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>No PRE Tags\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>If you don’t want your debug output to be enclosed in PRE tags, simply set the following in your extension:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Debug_This::$no_pre = true;\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Saved Queries and Execution Time\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Retrieve saved queries and execution time by using the following static properties:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>Debug_This::$execution_time\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>Debug_This::$queries\u003C\u002Fcode> – SAVEQUERIES must defined as true\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>URL Helpers\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>Debug_This::get_current_debug_url()\u003C\u002Fcode> – current URL with the debug query\u003C\u002Fli>\n\u003Cli>\u003Ccode>Debug_This::get_escape_url()\u003C\u002Fcode> – used for the debug escape link that links to original page URL\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>WP Actions\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ccode>debug_this\u003C\u002Fcode> – receives the $mode arg – outputs the debug code sent from the extension modes. The default action is set to priority 5. This allows you to prepend or append any output without conflict using less or greater priorities.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>WP Filters\u003C\u002Fh4>\n\u003Cp>There are a few filters you can use to customize Debug This to your needs:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>debug_this_template\u003C\u002Fcode> – receives $template arg – Use your own template\u003C\u002Fli>\n\u003Cli>\u003Ccode>debug_this_default_mode\u003C\u002Fcode>  – receives $mode arg – Alters the mode for the parent DT admin bar button link.\u003C\u002Fli>\n\u003Cli>\u003Ccode>debug_this_output\u003C\u002Fcode> – receives $output, $mode args – Filter debug content before it’s rendered\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>JavaScript\u003C\u002Fh4>\n\u003Cp>To access the built-in Debug This JS functionality, enqueue your custom script with the dependency set to \u003Ccode>debug-this\u003C\u002Fcode>. Your script will inherit a jQuery dependency.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Object: debugThis\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>debugThis.mode\u003C\u002Fcode> – current mode\u003C\u002Fli>\n\u003Cli>\u003Ccode>debugThis.defaultMode\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>debugThis.template\u003C\u002Fcode> – current included template\u003C\u002Fli>\n\u003Cli>\u003Ccode>debugThis.queryVar\u003C\u002Fcode> – the defined query string variable\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Functions:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>isDebug()\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>getDebugMode()\u003C\u002Fcode> – uses \u003Ccode>isDebug()\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Events:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>A jQuery \u003Ccode>debug-this\u003C\u002Fcode> event is fired from the footer. You can hook into this event with the following;\u003C\u002Fp>\n\u003Cpre>\u003Ccode>jQuery(document).bind('debug-this', function(event, debugThis){\n    console.log(debugThis);\n});\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Helper Functions\u003C\u002Fh4>\n\u003Cp>There are three included functions to help you work with files.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>debug_this_get_file_ownership($file)\u003C\u002Fcode> – returns \u003Ccode>array('name' => $name, 'group' => $group)\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>debug_this_get_file_perms($file)\u003C\u002Fcode> – returns string – Example: 0775\u003C\u002Fli>\n\u003Cli>\u003Ccode>debug_this_convert_perms_to_rwx($perms)\u003C\u002Fcode> – returns string – converts permission number to RWX format – Example: 0755 folder becomes drwxr-xr-x\u003C\u002Fli>\n\u003C\u002Ful>\n","Peek under the hood with sixty debugging reports just one click away.",2000,158436,96,17,"2025-06-04T08:56:00.000Z","5.2","5.6",[20,99,100,101,24],"debugger","developer","hooks","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-this.0.6.7.zip",{"slug":104,"name":105,"version":106,"author":107,"author_profile":108,"description":109,"short_description":110,"active_installs":111,"downloaded":112,"rating":93,"num_ratings":113,"last_updated":114,"tested_up_to":115,"requires_at_least":116,"requires_php":97,"tags":117,"homepage":120,"download_link":121,"security_score":27,"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,8,"2021-01-18T16:09:00.000Z","5.6.0","4.7",[20,58,24,118,119],"testing","tests","https:\u002F\u002Fwww.screenfeed.fr\u002Fsf-abt\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsf-adminbar-tools.zip",{"slug":123,"name":124,"version":125,"author":126,"author_profile":127,"description":128,"short_description":129,"active_installs":72,"downloaded":130,"rating":72,"num_ratings":33,"last_updated":131,"tested_up_to":53,"requires_at_least":132,"requires_php":97,"tags":133,"homepage":136,"download_link":137,"security_score":138,"vuln_count":139,"unpatched_count":14,"last_vuln_date":140,"fetched_at":30},"variable-inspector","Variable Inspector","2.6.3","Bowo","https:\u002F\u002Fprofiles.wordpress.org\u002Fqriouslad\u002F","\u003Cp>Variable Inspector allows you to easily inspect your PHP $variables in a visually clean manner at a central dashboard in wp-admin. It aims to be an \u003Cstrong>easy and useful enough dev and debug tool\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>It provides \u003Cstrong>a single-line code\u003C\u002Fstrong> to inspect your variable (see “How to Use” below). Nothing is shown to site visitors nor being output on the frontend, and the \u003Cstrong>$variable content is nicely formatted for review\u003C\u002Fstrong> using \u003Ca href=\"https:\u002F\u002Fwww.php.net\u002Fmanual\u002Fen\u002Ffunction.var-dump.php\" rel=\"nofollow ugc\">var_dump()\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fwww.php.net\u002Fmanual\u002Fen\u002Ffunction.var-export.php\" rel=\"nofollow ugc\">var_export()\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fwww.php.net\u002Fmanual\u002Fen\u002Ffunction.print-r.php\" rel=\"nofollow ugc\">print_r()\u003C\u002Fa> on the inspector dashboard in wp-admin.\u003C\u002Fp>\n\u003Cp>It’s a real time-saver for scenarios where \u003Ca href=\"https:\u002F\u002Fxdebug.org\u002F\" rel=\"nofollow ugc\">Xdebug\u003C\u002Fa> or even something like \u003Ca href=\"https:\u002F\u002Fmyray.app\u002F\" rel=\"nofollow ugc\">Ray\u003C\u002Fa> is not ideal or simply an overkill. For example, when coding on a non-local environment via tools like \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcode-snippets\u002F\" rel=\"ugc\">Code Snippets\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fwpcodebox.com\u002F\" rel=\"nofollow ugc\">WPCodeBox\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fdplugins.com\u002Fproducts\u002Fscripts-organizer\u002F\" rel=\"nofollow ugc\">Scripts Organizer\u003C\u002Fa> or \u003Ca href=\"https:\u002F\u002Fwww.cleanplugins.com\u002Fproducts\u002Fadvanced-scripts\u002F\" rel=\"nofollow ugc\">Advanced Scripts\u003C\u002Fa>. Additionally, because it is a regular WordPress plugin, you simply install, activate and use without the need for complicated configuration.\u003C\u002Fp>\n\u003Ch3>What Users Say\u003C\u002Fh3>\n\u003Cp>\u003Cem>“\u003Cstrong>Huge time-saver when working with PHP variables\u003C\u002Fstrong>.”\u003C\u002Fem> ~\u003Ca href=\"https:\u002F\u002Fdigwp.com\u002F2023\u002F06\u002Fplugins-troubleshoot-debug-wordpress\u002F\" rel=\"nofollow ugc\">Jeff Starr\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cem>“\u003Cstrong>Works great!\u003C\u002Fstrong> Love this thing.”\u003C\u002Fem> ~\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Ftopic\u002Fworks-great-8269\u002F\" rel=\"ugc\">Josh\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cem>“\u003Cstrong>Every developer need it.\u003C\u002Fstrong> You can debug easily every variable.”\u003C\u002Fem> ~\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Ftopic\u002Fawsome-plugin-that-every-developer-need-it\u002F\" rel=\"ugc\">Pexle Chris\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cem>“\u003Cstrong>All I need\u003C\u002Fstrong>. Enough to test the function of snippets. Works flawless.”\u003C\u002Fem> ~\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Ftopic\u002Fall-i-need-39\u002F\" rel=\"ugc\">@tesig\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cem>“\u003Cstrong>It does what it does very well\u003C\u002Fstrong>, and doesn’t try to do everything.”\u003C\u002Fem> ~\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Ftopic\u002Fexactly-what-i-needed-868\u002F\" rel=\"ugc\">@swb1\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>How to Use\u003C\u002Fh3>\n\u003Cp>Simply place the following line anywhere in your code after the \u003Ccode>$variable_name\u003C\u002Fcode> you’d like to inspect:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>do_action( 'inspect', [ 'variable_name', $variable_name ] );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>If you’d like to record the originating PHP file and line number, append the PHP magic constants \u003Ccode>__FILE__\u003C\u002Fcode> and \u003Ccode>__LINE__\u003C\u002Fcode> as follows.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>do_action( 'inspect', [ 'variable_name', $variable_name, __FILE__, __LINE__ ] );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>This would help you locate and clean up the inspector lines once you’re done debugging.\u003C\u002Fp>\n\u003Ch3>Give Back\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbowo.io\u002Fvi-rvw-dsc\" rel=\"nofollow ugc\">A nice review\u003C\u002Fa> would be great!\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbowo.io\u002Fvi-fdbk-dsc\" rel=\"nofollow ugc\">Give feedback\u003C\u002Fa> and help improve future versions.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbowo.io\u002Fvi-gthb-dsc\" rel=\"nofollow ugc\">Github repo\u003C\u002Fa> to contribute code.\u003C\u002Fli>\n\u003Cli>Sponsor my work with as little as USD 1 \u003Ca href=\"https:\u002F\u002Fbowo.io\u002Fvi-sp-gth-rdm\" rel=\"nofollow ugc\">monthly\u003C\u002Fa> or \u003Ca href=\"https:\u002F\u002Fbowo.io\u002Fvi-sp-ppl-rdm\" rel=\"nofollow ugc\">one-time\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>PRO Version\u003C\u002Fh3>\n\u003Cp>If you need something more versatile for larger, more complex projects, these \u003Ca href=\"https:\u002F\u002Fbowo.io\u002Fvi-up-hstd-dsc\" rel=\"nofollow ugc\">PRO features\u003C\u002Fa> might come in handy:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>vi( $variable )\u003C\u002Fstrong> inspector to replace the do_action() above and automatically includes the file path and line number. Or, use \u003Cstrong>vis( $variable_name, ‘variable_name’ )\u003C\u002Fstrong> when inspecting in\u002Fvia code snippets plugins (Code Snippets, WPCodeBox, Scripts Organizer, etc.) or custom code module of page builders (Bricks, Oxygen Builder, etc.)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>dump_print_r\u003C\u002Fstrong> and \u003Cstrong>dump_print_tree\u003C\u002Fstrong> viewers: both viewers combines var_dump and print_r, with the later allowing for collapsing and expanding data nodes, which is especially useful for inspecting long and complex arrays and objects.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>kint\u003C\u002Fstrong> viewer: an advanced viewer with table view for multi-dimensional arrays, node access path info, capability to search inside variables, pop-up window viewing and advanced info for your complex objects, e.g. available methods and static class properties.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Categorize and filter results by color\u003C\u002Fstrong>. This, for example, allows you to categorize $variables according to which stage they’re in inside your code.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Add counter or notes\u003C\u002Fstrong> to inspection results. Another way to tag $variables and provide context for the inspection results.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Search filter\u003C\u002Fstrong>: easily find certain $variables by name and type.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>View up to 250 results\u003C\u002Fstrong>. The free version is limited to 25 results.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Individual and bulk deletion\u003C\u002Fstrong> of results. Easily clean up your inspection dashboard from obsolete results you no longer need to reference. You can also select certain variables in bulk.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fbowo.io\u002Fvi-pro-scrsht-rdm\" rel=\"nofollow ugc\">Click here\u003C\u002Fa> to see a screenshot of the \u003Ca href=\"https:\u002F\u002Fbowo.io\u002Fvi-up-hstd-dsc\" rel=\"nofollow ugc\">PRO version\u003C\u002Fa> or see below in the screenshots section.\u003C\u002Fp>\n\u003Ch3>What PRO Users Say\u003C\u002Fh3>\n\u003Cp>\u003Cem>“I was looking for a tool like this for a while. \u003Cstrong>Great solution!\u003C\u002Fstrong> Love this thing.”\u003C\u002Fem> ~Marco Frodl\u003C\u002Fp>\n\u003Cp>\u003Cem>“I have used it for a couple of days and it has helped me a lot to \u003Cstrong>go faster when debugging\u003C\u002Fstrong>.””\u003C\u002Fem> ~Javier Sor\u003C\u002Fp>\n\u003Cp>\u003Cem>“I’ve only just started using it and it \u003Cstrong>really helps me get my head around the code of a plugin\u003C\u002Fstrong> I’m trying to customise”\u003C\u002Fem> ~Tim Dickinson\u003C\u002Fp>\n\u003Cp>\u003Cem>“I’ve been testing it and I really like it. It \u003Cstrong>helps a lot and saves a lot of time in development\u003C\u002Fstrong>. It’s also compatible with Oxygen, Bricks, WPCodeBox, etc.”\u003C\u002Fem> ~Juan Jose Gonzalez, oxygenados.com\u003C\u002Fp>\n\u003Cp>\u003Cem>“I just bought this! \u003Cstrong>Great plugin\u003C\u002Fstrong> – thank you for the hard work!”\u003C\u002Fem> ~Tim Dickinson\u003C\u002Fp>\n\u003Cp>\u003Cem>“I used to use Ray locally, I’m also using Xdebug a lot .. if I need to debug some variables, I use Query Monitor. I bought this, because \u003Cstrong>the UI is nice, it has all those good features from both worlds\u003C\u002Fstrong>.”\u003C\u002Fem> ~Peter Morvay\u003C\u002Fp>\n\u003Cp>\u003Cem>“Worth the buy! \u003Cstrong>It is really good… great for debugging\u003C\u002Fstrong>. Specially, when you want to write custom code or understand some snippet ChatGPT gave you.”\u003C\u002Fem> ~John D\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fbowo.io\u002Fvi-up-hstd-dsc\" rel=\"nofollow ugc\">Get the PRO version now!\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>Check These Out Too\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fadmin-site-enhancements\u002F\" rel=\"ugc\">Admin and Site Enhancements\u003C\u002Fa> helps you to easily enhance various admin workflows and site aspects while replacing multiple plugins doing it.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fsystem-dashboard\u002F\" rel=\"ugc\">System Dashboard\u003C\u002Fa>: Central dashboard to monitor various WordPress components, processes and data, including the server.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdebug-log-manager\u002F\" rel=\"ugc\">Debug Log Manager\u003C\u002Fa>: Log PHP, database and JavaScript errors via WP_DEBUG with one click. Conveniently create, view, filter and clear the debug.log file.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbowo.io\u002Fvi-wpn-dsc\" rel=\"nofollow ugc\">WordPress Newsboard\u003C\u002Fa>: The latest news, articles, podcasts and videos from 100+ WordPress-focused sources.\u003C\u002Fli>\n\u003C\u002Ful>\n","Inspect PHP variables on a central dashboard in wp-admin for convenient debugging.",73407,"2026-01-16T12:45:00.000Z","4.8",[20,100,134,135],"php-variables","variable-dump","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fvariable-inspector\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fvariable-inspector.2.6.3.zip",77,2,"2025-04-04 00:00:00",{"attackSurface":142,"codeSignals":201,"taintFlows":268,"riskAssessment":269,"analyzedAt":274},{"hooks":143,"ajaxHandlers":197,"restRoutes":198,"shortcodes":199,"cronEvents":200,"entryPointCount":28,"unprotectedCount":28},[144,150,155,159,163,167,170,175,177,181,184,186,192],{"type":145,"name":146,"callback":147,"file":148,"line":149},"action","shutdown","saveVersion","classes\\class.admin_page.php",93,{"type":145,"name":151,"callback":152,"priority":153,"file":148,"line":154},"plugin_action_links","setPluginActionLinks",15,106,{"type":145,"name":156,"callback":157,"file":148,"line":158},"admin_menu","setAdminMenu",108,{"type":145,"name":160,"callback":161,"file":148,"line":162},"admin_enqueue_scripts","enqueueScripts",109,{"type":145,"name":164,"callback":165,"file":148,"line":166},"admin_footer","closure",545,{"type":145,"name":160,"callback":168,"file":148,"line":169},"wp_enqueue_media",546,{"type":145,"name":171,"callback":172,"file":173,"line":174},"wp_footer","echo_debug","classes\\class.io.php",35,{"type":145,"name":164,"callback":172,"file":173,"line":176},36,{"type":145,"name":178,"callback":178,"file":179,"line":180},"plugins_loaded","classes\\init.php",48,{"type":145,"name":182,"callback":182,"file":179,"line":183},"wp_enqueue_scripts",51,{"type":145,"name":160,"callback":182,"file":179,"line":185},52,{"type":187,"name":188,"callback":189,"priority":11,"file":190,"line":191},"filter","qm\u002Foutputter\u002Fhtml","register_output","classes\\query_monitor\\collector.php",25,{"type":187,"name":193,"callback":156,"priority":194,"file":195,"line":196},"qm\u002Foutput\u002Fmenus",60,"classes\\query_monitor\\output.php",22,[],[],[],[],{"dangerousFunctions":202,"sqlUsage":203,"outputEscaping":205,"fileOperations":28,"externalRequests":28,"nonceChecks":14,"capabilityChecks":28,"bundledLibraries":267},[],{"prepared":28,"raw":28,"locations":204},[],{"escaped":11,"rawEcho":206,"locations":207},39,[208,211,213,215,217,219,222,223,224,225,226,228,229,230,231,232,233,235,236,237,238,240,242,243,244,246,248,249,250,252,253,255,257,258,259,260,262,264,265],{"file":148,"line":209,"context":210},515,"raw output",{"file":148,"line":212,"context":210},516,{"file":148,"line":214,"context":210},519,{"file":148,"line":216,"context":210},524,{"file":148,"line":218,"context":210},567,{"file":220,"line":221,"context":210},"classes\\class.helper.php",50,{"file":220,"line":221,"context":210},{"file":220,"line":183,"context":210},{"file":220,"line":183,"context":210},{"file":220,"line":185,"context":210},{"file":220,"line":227,"context":210},54,{"file":220,"line":227,"context":210},{"file":220,"line":194,"context":210},{"file":220,"line":194,"context":210},{"file":220,"line":194,"context":210},{"file":220,"line":194,"context":210},{"file":220,"line":234,"context":210},66,{"file":220,"line":234,"context":210},{"file":220,"line":234,"context":210},{"file":220,"line":234,"context":210},{"file":220,"line":239,"context":210},73,{"file":220,"line":241,"context":210},74,{"file":220,"line":241,"context":210},{"file":220,"line":241,"context":210},{"file":220,"line":245,"context":210},75,{"file":220,"line":247,"context":210},83,{"file":220,"line":247,"context":210},{"file":220,"line":247,"context":210},{"file":220,"line":251,"context":210},95,{"file":220,"line":251,"context":210},{"file":220,"line":254,"context":210},105,{"file":220,"line":256,"context":210},111,{"file":220,"line":256,"context":210},{"file":220,"line":256,"context":210},{"file":220,"line":256,"context":210},{"file":220,"line":261,"context":210},126,{"file":220,"line":263,"context":210},150,{"file":173,"line":256,"context":210},{"file":173,"line":266,"context":210},120,[],[],{"summary":270,"deductions":271},"The \"query-monitor-extension-checking-variables\" plugin v4.0.0 demonstrates a generally strong security posture based on the provided static analysis. The complete absence of direct entry points like AJAX handlers, REST API routes, shortcodes, and cron events significantly limits the potential attack surface. Furthermore, the code shows excellent practice by using prepared statements for all SQL queries and not performing any file operations or external HTTP requests, which are common sources of vulnerabilities.\n\nHowever, a notable concern is the low percentage (20%) of properly escaped output. With 49 total outputs, this indicates that a significant number of them might be vulnerable to Cross-Site Scripting (XSS) attacks if user-supplied data is involved. While there are no recorded vulnerabilities or taint flows indicating critical or high risks, the potential for XSS due to insufficient output escaping should not be overlooked. The presence of a nonce check is positive, but the absence of capability checks for any potential (though currently non-existent) entry points is a minor area for improvement in a comprehensive security model.\n\nIn conclusion, the plugin benefits from a minimal attack surface and responsible handling of database interactions. The primary weakness lies in the output escaping, which, if not addressed, could lead to medium or low severity vulnerabilities. The lack of past vulnerabilities is a positive sign, suggesting developers are attentive to security, but the current code analysis highlights an area requiring attention.",[272],{"reason":273,"points":113},"Low percentage of properly escaped output","2026-03-17T00:29:51.401Z",{"wat":276,"direct":285},{"assetPaths":277,"generatorPatterns":280,"scriptPaths":281,"versionParams":282},[278,279],"\u002Fwp-content\u002Fplugins\u002Fquery-monitor-extension-checking-variables\u002Fassets\u002Fjs\u002Fcheck-var.js","\u002Fwp-content\u002Fplugins\u002Fquery-monitor-extension-checking-variables\u002Fassets\u002Fcss\u002Fcheck-var.css",[],[278],[283,284],"query-monitor-extension-checking-variables\u002Fassets\u002Fjs\u002Fcheck-var.js?ver=","query-monitor-extension-checking-variables\u002Fassets\u002Fcss\u002Fcheck-var.css?ver=",{"cssClasses":286,"htmlComments":287,"htmlAttributes":288,"restEndpoints":289,"jsGlobals":290,"shortcodeOutput":292},[],[],[],[],[291],"QMCVar",[]]