[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f4nYmmjdiFxU0uqXTPbDQkE0Nilsl9rBaOcpyyLD1_aM":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":13,"last_updated":14,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":18,"homepage":21,"download_link":22,"security_score":23,"vuln_count":13,"unpatched_count":13,"last_vuln_date":24,"fetched_at":25,"vulnerabilities":26,"developer":27,"crawl_stats":24,"alternatives":35,"analysis":138,"fingerprints":167},"vimeotheque-debug","Vimeotheque Debug","1.0.1","CodeFlavors","https:\u002F\u002Fprofiles.wordpress.org\u002Fcodeflavors\u002F","\u003Cp>\u003Cstrong>Vimeotheque Debug\u003C\u002Fstrong> is an add-on for WordPress plugin \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcodeflavors-vimeo-video-post-lite\u002F\" rel=\"ugc\">Vimeotheque\u003C\u002Fa> which logs various debug messages emitted by Vimeotheque when certain actions are taken (ie. video importing, video queries, featured image imports and so on).\u003C\u002Fp>\n\u003Cp>The plugin will add a new menu item called “Debug log” under Vimeotheque’s admin menu which will point to the debug page that shows the latest messages emitted by Vimeotheque.\u003C\u002Fp>\n\u003Cp>The debugger requires plugin Vimeotheque 2.0 (or above) to be activated in order to capture the messages.\u003C\u002Fp>\n","Debug add-on for plugin Vimeotheque by CodeFlavors",50,1451,0,"","6.5.8","5.2","7.4",[19,20],"debug","vimeotheque","https:\u002F\u002Fgithub.com\u002Fconstantin-b\u002Fvimeotheque-debug\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fvimeotheque-debug.zip",100,null,"2026-03-15T10:48:56.248Z",[],{"slug":28,"display_name":7,"profile_url":8,"plugin_count":29,"total_installs":30,"avg_security_score":31,"avg_patch_time_days":32,"trust_score":33,"computed_at":34},"codeflavors",3,2080,95,7,97,"2026-04-04T05:01:50.632Z",[36,61,79,98,120],{"slug":37,"name":38,"version":39,"author":40,"author_profile":41,"description":42,"short_description":43,"active_installs":44,"downloaded":45,"rating":46,"num_ratings":47,"last_updated":48,"tested_up_to":49,"requires_at_least":50,"requires_php":17,"tags":51,"homepage":56,"download_link":57,"security_score":58,"vuln_count":29,"unpatched_count":13,"last_vuln_date":59,"fetched_at":60},"wp-crontrol","WP Crontrol","1.21.0","John Blackbourn","https:\u002F\u002Fprofiles.wordpress.org\u002Fjohnbillion\u002F","\u003Cp>WP Crontrol enables you to take control of the scheduled cron events on your WordPress website or WooCommerce store. From the admin screens you can:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>View all scheduled cron events along with their arguments, schedule, callback functions, and when they are next due.\u003C\u002Fli>\n\u003Cli>Edit, delete, pause, resume, and immediately run cron events.\u003C\u002Fli>\n\u003Cli>Add new cron events.\u003C\u002Fli>\n\u003Cli>Bulk delete cron events.\u003C\u002Fli>\n\u003Cli>Add and remove custom cron schedules.\u003C\u002Fli>\n\u003Cli>Export and download cron event lists as a CSV file.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>WP Crontrol is aware of timezones, will alert you to events that have no actions or that have missed their schedule, and will show you a helpful warning message if it detects any problems with your cron system.\u003C\u002Fp>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Go to the \u003Ccode>Tools \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Cron Events\u003C\u002Fcode> menu to manage cron events.\u003C\u002Fli>\n\u003Cli>Go to the \u003Ccode>Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Cron Schedules\u003C\u002Fcode> menu to manage cron schedules.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Documentation\u003C\u002Fh3>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwp-crontrol.com\u002Fdocs\u002Fhow-to-use\u002F\" rel=\"nofollow ugc\">Extensive documentation on how to use WP Crontrol and how to get help for error messages that it shows is available on the WP Crontrol website\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>For site owners\u003C\u002Fh3>\n\u003Cp>Owners of WordPress websites and WooCommerce stores use WP Crontrol to ensure that scheduled cron events run correctly and efficiently. By providing complete control over cron events, WP Crontrol helps you:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Improve reliability\u003C\u002Fstrong>: Address missed or failed cron events, ensuring your website or WooCommerce store continues to function as expected.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Enhance security\u003C\u002Fstrong>: Monitor and control cron events to ensure automatic update checks are performed as they should.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Simplify management\u003C\u002Fstrong>: Add, edit, delete, and pause cron events from a user-friendly interface, without needing to write any code.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Gain insights\u003C\u002Fstrong>: Export cron event data for analysis or reporting.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Action Scheduler compatibility\u003C\u002Fstrong>: Full support for the Action Scheduler system in WooCommerce, which is used to process recurring payments, subscriptions, and background orders.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Clarity of times and timezones\u003C\u002Fstrong>: All times are shown with a clear and accurate indication of which timezone applies. No more guesswork!\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>For developers\u003C\u002Fh3>\n\u003Cp>Developers use WP Crontrol to streamline and debug their WordPress development process:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Enhanced debugging\u003C\u002Fstrong>: Identify and troubleshoot issues with scheduled tasks, ensuring your scheduled events and their callbacks run as expected.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Custom schedules\u003C\u002Fstrong>: Create and manage custom cron schedules to fit the specific needs of your website, plugins, or themes, providing greater flexibility than just the core schedules.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Efficient workflow\u003C\u002Fstrong>: Add, edit, and delete cron events directly from the WordPress admin interface, saving time and reducing the need for manual coding.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Insightful monitoring\u003C\u002Fstrong>: Get insight into the performance and behavior of your scheduled tasks, allowing for optimization and better resource management.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Accurate debugging\u003C\u002Fstrong>: WP Crontrol goes to great lengths to ensure that running an event manually does so in a manner which exactly matches how WordPress core runs schdeuled events. This ensures that you can debug events accurately and with confidence.\u003C\u002Fli>\n\u003C\u002Ful>\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\u002Fquery-monitor\u002F\" rel=\"ugc\">Query Monitor\u003C\u002Fa> is the developer tools panel for WordPress.\u003C\u002Fli>\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\u003C\u002Ful>\n\u003Ch3>Privacy Statement\u003C\u002Fh3>\n\u003Cp>WP Crontrol is private by default and always will be. It does not send data to any third party, nor does it include any third party resources. \u003Ca href=\"https:\u002F\u002Fwp-crontrol.com\u002Fprivacy\u002F\" rel=\"nofollow ugc\">WP Crontrol’s full privacy statement can be found here\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Accessibility Statement\u003C\u002Fh3>\n\u003Cp>WP Crontrol aims to be fully accessible to all of its users. \u003Ca href=\"https:\u002F\u002Fwp-crontrol.com\u002Faccessibility\u002F\" rel=\"nofollow ugc\">WP Crontrol’s full accessibility statement can be found here\u003C\u002Fa>.\u003C\u002Fp>\n","WP Crontrol enables you to take control of the cron events on your WordPress website.",300000,7578206,90,163,"2026-01-28T21:40:00.000Z","6.9.4","6.4",[52,53,19,54,55],"cron","crontrol","woocommerce","wp-cron","https:\u002F\u002Fwp-crontrol.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-crontrol.1.21.0.zip",96,"2025-08-21 00:00:00","2026-03-15T15:16:48.613Z",{"slug":62,"name":63,"version":64,"author":40,"author_profile":41,"description":65,"short_description":66,"active_installs":67,"downloaded":68,"rating":69,"num_ratings":70,"last_updated":71,"tested_up_to":49,"requires_at_least":72,"requires_php":17,"tags":73,"homepage":77,"download_link":78,"security_score":23,"vuln_count":13,"unpatched_count":13,"last_vuln_date":24,"fetched_at":60},"query-monitor","Query Monitor – The developer tools panel for WordPress","3.20.2","\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.1",[19,74,75,76,62],"debug-bar","development","performance","https:\u002F\u002Fquerymonitor.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fquery-monitor.3.20.2.zip",{"slug":74,"name":80,"version":81,"author":82,"author_profile":83,"description":84,"short_description":85,"active_installs":86,"downloaded":87,"rating":88,"num_ratings":89,"last_updated":90,"tested_up_to":91,"requires_at_least":92,"requires_php":14,"tags":93,"homepage":94,"download_link":95,"security_score":23,"vuln_count":96,"unpatched_count":13,"last_vuln_date":97,"fetched_at":60},"Debug Bar","1.1.8","WordPress.org","https:\u002F\u002Fprofiles.wordpress.org\u002Fwordpressdotorg\u002F","\u003Cp>Adds a debug menu to the admin bar that shows query, cache, and other helpful debugging information.\u003C\u002Fp>\n\u003Cp>A must for developers!\u003C\u002Fp>\n\u003Cp>When \u003Ccode>WP_DEBUG\u003C\u002Fcode> is enabled it also tracks PHP Warnings and Notices to make them easier to find.\u003C\u002Fp>\n\u003Cp>When \u003Ccode>SAVEQUERIES\u003C\u002Fcode> is enabled the mysql queries are tracked and displayed.\u003C\u002Fp>\n\u003Cp>To enable these options, add the following code to your \u003Ccode>wp-config.php\u003C\u002Fcode> file:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'WP_DEBUG', true );\ndefine( 'SAVEQUERIES', true );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Add a PHP\u002FMySQL console with the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdebug-bar-console\u002F\" rel=\"ugc\">Debug Bar Console plugin\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>There are numerous other add-ons available to get more insight into, for instance, the registered Post Types, Shortcodes, WP Cron, Language file loading, Actions and Filters and so on. Just \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fsearch\u002Fdebug+bar\u002F\" rel=\"ugc\">search the plugin directory for ‘Debug Bar’\u003C\u002Fa>.\u003C\u002Fp>\n","Adds a debug menu to the admin bar that shows query, cache, and other helpful debugging information.",20000,2087029,82,68,"2026-03-01T20:00:00.000Z","7.0","3.4",[19],"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdebug-bar\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-bar.1.1.8.zip",1,"2013-05-15 00:00:00",{"slug":99,"name":100,"version":101,"author":102,"author_profile":103,"description":104,"short_description":105,"active_installs":106,"downloaded":107,"rating":23,"num_ratings":108,"last_updated":109,"tested_up_to":110,"requires_at_least":111,"requires_php":112,"tags":113,"homepage":116,"download_link":117,"security_score":118,"vuln_count":32,"unpatched_count":13,"last_vuln_date":119,"fetched_at":60},"debug-log-manager","Debug Log Manager – Conveniently Monitor and Inspect Errors","2.4.3","Bowo","https:\u002F\u002Fprofiles.wordpress.org\u002Fqriouslad\u002F","\u003Cp>Debug Log Manager allows you to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Enable \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Farticle\u002Fdebugging-in-wordpress\u002F\" rel=\"ugc\">WP_DEBUG\u003C\u002Fa> with one click to log PHP, database and JavaScript errors\u003C\u002Fstrong> when you need to, and disable it when you’re done. No need to manually edit wp-config.php file. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Create the debug.log file for you\u003C\u002Fstrong> in a non-default location with a custom file name for enhanced security. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Copy the content of the default \u002F existing debug.log file\u003C\u002Fstrong> into the custom debug.log file, and delete the default \u002F existing debug.log file. So there is continuation in logging and enhanced security going forward.\u003C\u002Fli>\n\u003Cli>Parse the debug.log file and \u003Cstrong>view distinct errors and when they last occurred\u003C\u002Fstrong>, which is better than looking at the raw log file (potentially) full of repetitive errors. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Quickly find and filter more specific errors\u003C\u002Fstrong> for your debugging work.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Make error details easier to read\u003C\u002Fstrong> by identifying error source (core \u002F plugin \u002F theme) and separating file path and line number.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Easily view files where PHP errors occurred\u003C\u002Fstrong>. This includes WordPress core, plugin and theme files.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Enable auto-refresh\u003C\u002Fstrong> to automatically load new log entries. No need to manually reload the browser tab, or to \u003Ccode>tail -f\u003C\u002Fcode> the log file on the command line.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Easily clear the debug.log file\u003C\u002Fstrong> to save disk space and more easily observe newly occurring errors on your site.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Show an indicator on the admin bar\u003C\u002Fstrong> when error logging is enabled.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Add a dashboard widget\u003C\u002Fstrong> showing the latest errors logged.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Use \u003Ccode>error_log()\u003C\u002Fcode>\u003C\u002Fstrong> to output error info into your debug log. e.g. \u003Ccode>error_log( $error_message )\u003C\u002Fcode> for simple, string-based error message, or \u003Ccode>error_log( json_encode( $error ) )\u003C\u002Fcode> when inspecting a more complex error info, e.g. array or object.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>A simpler and more compact version of Debug Log Manager is included as part of the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fsystem-dashboard\u002F\" rel=\"ugc\">System Dashboard plugin\u003C\u002Fa>, should you prefer a single plugin that does more.\u003C\u002Fp>\n\u003Ch3>What Users Say\u003C\u002Fh3>\n\u003Cp>\u003Cem>“This is \u003Cstrong>a great plugin for dev\u003C\u002Fstrong> especially for people who tinker in the code.”\u003C\u002Fem> ~\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Ftopic\u002Fgreat-for-dev\u002F\" rel=\"ugc\">PK Son\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cem>“I have used a couple of other logger plugins and \u003Cstrong>this is by far the best one\u003C\u002Fstrong>.”\u003C\u002Fem> ~\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Ftopic\u002Fmust-have-plugin-485\u002F\" rel=\"ugc\">Brian Henry\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cem>“\u003Cstrong>Another massive time-saving tool.\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\u003Ch3>Give Back\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbowo.io\u002Freview-dlm\" rel=\"nofollow ugc\">A nice review\u003C\u002Fa> would be great!\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbowo.io\u002Ffeedback-dlm\" rel=\"nofollow ugc\">Give feedback\u003C\u002Fa> and help improve future versions.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Fdebug-log-manager\u002F\" rel=\"nofollow ugc\">Help translate\u003C\u002Fa> into your language.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbowo.io\u002Fgithub-dlm\" rel=\"nofollow ugc\">Github repo\u003C\u002Fa> to contribute code.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbowo.io\u002Fdotorg-sponsor-dlm\" rel=\"nofollow ugc\">Sponsor\u003C\u002Fa> my work.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Check These Out Too\u003C\u002Fh3>\n\u003Cul>\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\u002Fvariable-inspector\u002F\" rel=\"ugc\">Variable Inspector\u003C\u002Fa>: Inspect PHP variables on a central dashboard in wp-admin for convenient debugging.\u003C\u002Fli>\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\u002Fwww.wpnewsboard.com\u002F\" 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","Log PHP, database and JavaScript errors via WP_DEBUG with one click. Conveniently create, view, filter and clear the debug.log file.",10000,116535,24,"2025-09-24T02:30:00.000Z","6.8.5","4.6","5.6",[19,114,115],"developer","errors","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdebug-log-manager\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-log-manager.2.4.3.zip",91,"2025-04-18 00:00:00",{"slug":121,"name":122,"version":123,"author":124,"author_profile":125,"description":126,"short_description":127,"active_installs":106,"downloaded":128,"rating":23,"num_ratings":129,"last_updated":130,"tested_up_to":110,"requires_at_least":16,"requires_php":112,"tags":131,"homepage":134,"download_link":135,"security_score":118,"vuln_count":136,"unpatched_count":13,"last_vuln_date":137,"fetched_at":60},"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.",432358,19,"2024-12-02T19:42:00.000Z",[19,132,133],"support","wp-config","https:\u002F\u002Fgithub.com\u002Fafragen\u002Fwp-debugging","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-debugging.2.12.2.zip",2,"2022-01-24 00:00:00",{"attackSurface":139,"codeSignals":154,"taintFlows":162,"riskAssessment":163,"analyzedAt":166},{"hooks":140,"ajaxHandlers":150,"restRoutes":151,"shortcodes":152,"cronEvents":153,"entryPointCount":13,"unprotectedCount":13},[141,147],{"type":142,"name":143,"callback":144,"file":145,"line":146},"action","admin_notices","vmtq_debugger_no_plugin","index.php",26,{"type":142,"name":143,"callback":148,"file":145,"line":149},"vmtq_debugger_fail_version",28,[],[],[],[],{"dangerousFunctions":155,"sqlUsage":156,"outputEscaping":158,"fileOperations":13,"externalRequests":13,"nonceChecks":13,"capabilityChecks":13,"bundledLibraries":161},[],{"prepared":13,"raw":13,"locations":157},[],{"escaped":159,"rawEcho":13,"locations":160},4,[],[],[],{"summary":164,"deductions":165},"The \"vimeotheque-debug\" plugin v1.0.1 exhibits a strong security posture based on the provided static analysis. There are no identified vulnerabilities in its attack surface, code signals, or taint analysis. The absence of AJAX handlers, REST API routes, shortcodes, cron events, and file operations significantly limits the plugin's potential entry points for attackers. Furthermore, the code demonstrates good development practices by not using dangerous functions, all SQL queries are prepared, and all output is properly escaped. The plugin also avoids external HTTP requests and bundled libraries, further reducing its attack surface. The plugin's vulnerability history is clean, with no recorded CVEs, indicating a history of secure development or minimal exposure to known vulnerabilities. Overall, this plugin appears to be very secure.",[],"2026-03-16T21:52:04.070Z",{"wat":168,"direct":177},{"assetPaths":169,"generatorPatterns":172,"scriptPaths":173,"versionParams":174},[170,171],"\u002Fwp-content\u002Fplugins\u002Fvimeotheque-debug\u002Fassets\u002Fcss\u002Fstyle.css","\u002Fwp-content\u002Fplugins\u002Fvimeotheque-debug\u002Fassets\u002Fjs\u002Fscript.js",[],[171],[175,176],"vimeotheque-debug\u002Fassets\u002Fcss\u002Fstyle.css?ver=","vimeotheque-debug\u002Fassets\u002Fjs\u002Fscript.js?ver=",{"cssClasses":178,"htmlComments":179,"htmlAttributes":180,"restEndpoints":181,"jsGlobals":182,"shortcodeOutput":183},[],[],[],[],[],[]]