[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fi31A2BJyaVpEfxBFGexc4avURLvvOuNNQ6CktJhLI-4":3,"$fqTJ-Ez_-7rvbOxd_NywezIHO1y1fszO1joW_sA4-cvM":211,"$ftXRt5J3X4vFJewzsHQwFWKgAgyReYUii1tEUDRy0JUE":216},{"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":11,"last_updated":14,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":18,"homepage":24,"download_link":25,"security_score":13,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28,"discovery_status":29,"vulnerabilities":30,"developer":31,"crawl_stats":27,"alternatives":38,"analysis":150,"fingerprints":198},"debug-mo-translations","Debug MO Translations","1.3.1","closemarketing","https:\u002F\u002Fprofiles.wordpress.org\u002Fclosemarketing\u002F","\u003Cp>It gives you more information about all domains and translated mo files loaded in the actual installation, so you can debug what’s the problem with a plugin, theme, etc.\u003C\u002Fp>\n\u003Cp>Only shows the debug info if you’re logged in in the footer.\u003C\u002Fp>\n\u003Cp>You’ll have a info of all plugins loaded, textdomain used, if file is found and then the path where is the function of theme or plugin loaded. You can see the screenshots.\u003C\u002Fp>\n\u003Ch3>Developers\u003C\u002Fh3>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fclosemarketing\u002Fdebug-mo-translations\" rel=\"nofollow ugc\">Official Repository GitHub\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>Links\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fclose.marketing\u002F\" rel=\"nofollow ugc\">Closemarketing\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fclosemarketing\u002F#content-plugins\" rel=\"nofollow ugc\">Closemarketing plugins\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Ftwitter.com\u002Fpedro_gaspar\" rel=\"nofollow ugc\">Pedro Mendonça\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n","Debugs all translated files that are loaded and not in WordPress.",10,7716,100,"2025-11-27T16:46:00.000Z","6.9.4","4.6","",[19,20,21,22,23],"debug","languages","mo","translate","translations","https:\u002F\u002Fgithub.com\u002Fclosemarketing\u002Fdebug-mo-translations","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-mo-translations.1.3.1.zip",0,null,"2026-04-16T10:56:18.058Z","no_bundle",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":32,"total_installs":33,"avg_security_score":34,"avg_patch_time_days":35,"trust_score":36,"computed_at":37},12,4710,93,30,89,"2026-05-20T03:58:14.956Z",[39,63,86,109,130],{"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":15,"requires_at_least":52,"requires_php":53,"tags":54,"homepage":58,"download_link":59,"security_score":60,"vuln_count":61,"unpatched_count":26,"last_vuln_date":62,"fetched_at":28},"query-monitor","Query Monitor","4.0.6","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>Thanks\u003C\u002Fh3>\n\u003Cp>The time that I spend maintaining this plugin and others is in part sponsored by:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fautomattic.com\u002F\" rel=\"nofollow ugc\">Automattic\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fservmask.com\u002F\" rel=\"nofollow ugc\">ServMask\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwp-staging.com\u002F\" rel=\"nofollow ugc\">WP Staging\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fsponsors\u002Fjohnbillion\" rel=\"nofollow ugc\">All my kind sponsors on GitHub\u003C\u002Fa>\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,19993201,98,465,"2026-04-11T11:53:00.000Z","6.1","7.4",[19,55,56,57,40],"debug-bar","development","performance","https:\u002F\u002Fquerymonitor.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fquery-monitor.4.0.6.zip",97,1,"2026-03-30 23:21:22",{"slug":64,"name":65,"version":66,"author":67,"author_profile":68,"description":69,"short_description":70,"active_installs":71,"downloaded":72,"rating":73,"num_ratings":74,"last_updated":75,"tested_up_to":76,"requires_at_least":77,"requires_php":78,"tags":79,"homepage":17,"download_link":83,"security_score":84,"vuln_count":61,"unpatched_count":26,"last_vuln_date":85,"fetched_at":28},"theme-translation-for-polylang","Theme and plugin translation for Polylang (TTfP)","3.4.9","Marcin Kazmierski","https:\u002F\u002Fprofiles.wordpress.org\u002Fmarcinkazmierski\u002F","\u003Ch4>What is “Theme and plugin translation for Polylang”?\u003C\u002Fh4>\n\u003Cp>Extension for Polylang plugin (Polylang is an extension to make multilingual WordPress websites.).\u003Cbr \u002F>\nPlugin is needed to translate the WordPress themes and plugins by Polylang.\u003C\u002Fp>\n\u003Ch4>How to configure it?\u003C\u002Fh4>\n\u003Cp>Select themes and plugins to find texts for translation by Polylang.\u003Cbr \u002F>\nIn admin dashboard:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Languages -> TTfP Settings\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>How it is work?\u003C\u002Fh4>\n\u003Cp>“Theme and plugin translation for Polylang” automatically searches all files of WordPress themes and plugins. It chooses from this file only those files with extensions:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>php\u003C\u002Fli>\n\u003Cli>inc\u003C\u002Fli>\n\u003Cli>twig\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>In addition, is implemented the integration with Timber library (read more: http:\u002F\u002Ftimber.upstatement.com) – which allows to translate twig’s skins in simple way.\u003Cbr \u002F>\nPlugin in searched skins or plugins chooses texts from Polylang functions, such as:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>_e(string $text, string $domain = ‘default’);\u003C\u002Fli>\n\u003Cli>__(string $text, string $domain = ‘default’);\u003C\u002Fli>\n\u003Cli>_x(string $text, string $context, string $domain = ‘default’);\u003C\u002Fli>\n\u003Cli>pll_e(string $text);\u003C\u002Fli>\n\u003Cli>pll__(string $text);\u003C\u002Fli>\n\u003Cli>esc_html(string $text);\u003C\u002Fli>\n\u003Cli>esc_html_e(string $text, string $domain = ‘default’);\u003C\u002Fli>\n\u003Cli>esc_html__(string $text, string $domain = ‘default’);\u003C\u002Fli>\n\u003Cli>_n(string $single, string $plural, int $number, string $domain = ‘default’);\u003C\u002Fli>\n\u003Cli>esc_attr_e(string $text, string $domain = ‘default’);\u003C\u002Fli>\n\u003Cli>esc_attr__(string $text, string $domain = ‘default’);\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>In your function.php, themes or plugins.\u003C\u002Fp>\n\u003Cp>For example:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003Cp>\u003C?php pll_e('My text'); ?>\u003C\u002Fp>\n\n\u003Cp>\u003C?php _e('My another text', 'my_theme'); ?>\u003C\u002Fp>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>On the timber context declare this functions like:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$context['pll_e'] = TimberHelper::function_wrapper('pll_e');\n\n$context['pll_'] = TimberHelper::function_wrapper('pll_');\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>See more on: \u003Ccode>https:\u002F\u002Fpolylang.wordpress.com\u002Fdocumentation\u002Fdocumentation-for-developers\u002Ffunctions-reference\u002F\u003C\u002Fcode>\u003Cbr \u002F>\nThese functions are defined by Polylang plugin for printing translations.\u003Cbr \u002F>\nThanks “Theme and plugin translation for Polylang” you can find these strings to translate and add to Polylang register on very simple way.\u003Cbr \u002F>\nAnd then you can translate these texts from the admin dashboard.\u003Cbr \u002F>\nThe scan result can be seen on the tab with translations:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Settings -> Languages -> String translation\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>or\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Languages -> String translation\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>You don’t need programs like poedit – you don’t change files with extensions like: \u003Ccode>.pot\u003C\u002Fcode>, \u003Ccode>.po\u003C\u002Fcode>, \u003Ccode>.mo\u003C\u002Fcode>.\u003Cbr \u002F>\n“Theme and plugin translation for Polylang” is highly efficient because the scanner is worked only on admin dashboard in tab:\u003Cbr \u002F>\nIn dashboard:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Settings -> Languages -> String translation\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>or\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Languages -> String translation\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Export and import string translation\u003C\u002Fh4>\n\u003Cp>In dashboard:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Languages -> TTfP Settings\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Filter reference\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>ttfp_domains\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Allows plugins and themes (in functions.php) to modify list of text domains (unique identifier for retrieving translated strings).\u003Cbr \u002F>\nList of text domains is displayed on “TTfP Settings” page to select them for translation by polylang engine.\u003C\u002Fp>\n\u003Cp>Example:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_filter('ttfp_domains', 'custom_ttfp_domains', 10, 1);\nfunction custom_ttfp_domains(array $domains):array\n {\n     $domains[] = \"my-custom-domain\";\n     return $domains;\n }\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Filter reference\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>ttfp_translation_access\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Returns whether the user has capability to view and edit translations provided by TTfP.\u003C\u002Fp>\n\u003Cp>Example:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_filter('ttfp_translation_access', 'custom_ttfp_translation_access', 10, 1);\nfunction custom_ttfp_translation_access(bool $hasAccess):bool\n {\n     return current_user_can('edit_posts');\n }\n\u003C\u002Fcode>\u003C\u002Fpre>\n","Theme and plugin translation using Polylang for WordPress. Extension for Polylang plugin.",10000,272542,94,35,"2025-03-15T15:35:00.000Z","6.6.5","5.7","7.0",[20,80,81,22,82],"multilanguage","polylang","translation","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ftheme-translation-for-polylang.3.4.9.zip",92,"2022-11-28 00:00:00",{"slug":87,"name":88,"version":89,"author":90,"author_profile":91,"description":92,"short_description":93,"active_installs":94,"downloaded":95,"rating":13,"num_ratings":96,"last_updated":97,"tested_up_to":98,"requires_at_least":99,"requires_php":99,"tags":100,"homepage":105,"download_link":106,"security_score":107,"vuln_count":61,"unpatched_count":26,"last_vuln_date":108,"fetched_at":28},"debug-log-config-tool","Debug Log – Manager Tool","2.0.1","Lukman Nakib","https:\u002F\u002Fprofiles.wordpress.org\u002Fpyrobd\u002F","\u003Cp>A comprehensive debugging toolkit for WordPress developers and site administrators. This plugin gives you complete control over WordPress debugging without editing wp-config.php files or using FTP.\u003C\u002Fp>\n\u003Ch4>Quick Demo\u003C\u002Fh4>\n\u003Cspan class=\"embed-youtube\" style=\"text-align:center; display: block;\">\u003Ciframe loading=\"lazy\" class=\"youtube-player\" width=\"750\" height=\"422\" src=\"https:\u002F\u002Fwww.youtube.com\u002Fembed\u002FD4K5zsLnILw?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent\" allowfullscreen=\"true\" style=\"border:0;\" sandbox=\"allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox\">\u003C\u002Fiframe>\u003C\u002Fspan>\n\u003Ch4>Key Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>WP-CLI Style Terminal\u003C\u002Fstrong>: Execute WordPress commands directly from your browser with syntax highlighting and auto-completion\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Database Tools\u003C\u002Fstrong>: Run SQL queries, view table structures, and optimize your database (super admin only)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Debug Constants Manager\u003C\u002Fstrong>: Toggle all WordPress debug constants with a single click\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Log Viewer\u003C\u002Fstrong>: View, filter, and analyze debug logs with syntax highlighting and error categorization\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Query Inspector\u003C\u002Fstrong>: Examine database queries with SAVEQUERIES support\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Email Notifications\u003C\u002Fstrong>: Get alerts when new errors appear in your logs\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Safe Mode\u003C\u002Fstrong>: Quickly disable all plugins except selected ones for troubleshooting\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Custom Log Paths\u003C\u002Fstrong>: Set custom log file locations with filter support\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Debug Constants Available\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>WP_DEBUG\u003C\u002Fstrong> – Default Value: true – Enables WordPress debug mode\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WP_DEBUG_LOG\u003C\u002Fstrong> – Default Value: true – Saves all errors to a debug.log file\u003C\u002Fli>\n\u003Cli>\u003Cstrong>SCRIPT_DEBUG\u003C\u002Fstrong> – Default Value: false – Uses development versions of core JS and CSS files\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WP_DEBUG_DISPLAY\u003C\u002Fstrong> – Default Value: false – Controls whether debug messages display on screen\u003C\u002Fli>\n\u003Cli>\u003Cstrong>SAVEQUERIES\u003C\u002Fstrong> – Default Value: false – Saves database queries for analysis\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Developer Tools\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Terminal Commands\u003C\u002Fstrong>: Use WP-CLI style commands like \u003Ccode>wp core version\u003C\u002Fcode> or \u003Ccode>wp plugin list\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Database Explorer\u003C\u002Fstrong>: Run SELECT queries and view results in a formatted table\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Stack Trace Analysis\u003C\u002Fstrong>: Visualize error stack traces for easier debugging\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Hook Inspector\u003C\u002Fstrong>: View all registered hooks and their callbacks\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Environment Detection\u003C\u002Fstrong>: Development features are automatically hidden in production\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cblockquote>\n\u003Cp>\u003Cstrong>Developer API\u003C\u002Fstrong>: Apply custom filters like \u003Ccode>apply_filters('wp_debuglog_log_file_path', $file);\u003C\u002Fcode> to extend functionality\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>Please note: Constant values will be restored on plugin deactivation as it was before activating the plugin.\u003C\u002Fp>\n","The \"Debug Log Config Tool\" simplifies debugging. Toggle logging,queries , view levels, clear logs from dashboard.",3000,56820,21,"2025-04-30T19:04:00.000Z","6.8.5","5.6",[19,101,102,103,104],"developer","log","remote-debug","tools","https:\u002F\u002Fnkb-bd.github.io\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-log-config-tool.2.0.1.zip",91,"2024-05-20 00:00:00",{"slug":110,"name":111,"version":112,"author":113,"author_profile":114,"description":115,"short_description":116,"active_installs":117,"downloaded":118,"rating":13,"num_ratings":119,"last_updated":120,"tested_up_to":121,"requires_at_least":122,"requires_php":17,"tags":123,"homepage":127,"download_link":128,"security_score":129,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"monkeyman-rewrite-analyzer","Monkeyman Rewrite Analyzer","1.0","Jan Fabry","https:\u002F\u002Fprofiles.wordpress.org\u002Fjanfabry\u002F","\u003Cp>This is a tool to understand your rewrite rules (“Pretty Permalinks”). It is indispensable if you are adding or modifying rules and want to understand how they work (or why they don’t work).\u003C\u002Fp>\n\u003Cp>It is only an analyzer, it does not change any rules for you. It parses the rules down to their components and shows the connection with the resulting query variables. It allows you to try out different URLs to see which rules will match and what the value of the different query variables will be (see screenshots).\u003C\u002Fp>\n\u003Cp>This plugin was written as a tool to help answering questions about rewrite rules on \u003Ca href=\"http:\u002F\u002Fwordpress.stackexchange.com\u002F\" rel=\"nofollow ugc\">the WordPress Stack Exchange\u003C\u002Fa>.\u003C\u002Fp>\n","Making sense of the rewrite mess. Display and play with your rewrite rules.",2000,74113,26,"2011-05-12T17:49:00.000Z","3.2.1","3.0",[19,56,124,125,126],"mod_rewrite","permalinks","rewrite","http:\u002F\u002Fwordpress.stackexchange.com\u002Fq\u002F3606\u002F8","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmonkeyman-rewrite-analyzer.1.0.zip",85,{"slug":131,"name":132,"version":133,"author":134,"author_profile":135,"description":136,"short_description":137,"active_installs":117,"downloaded":138,"rating":139,"num_ratings":140,"last_updated":141,"tested_up_to":98,"requires_at_least":16,"requires_php":142,"tags":143,"homepage":148,"download_link":149,"security_score":84,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"wp-safe-mode","WP Safe Mode","1.3","Marcus (aka @msykes)","https:\u002F\u002Fprofiles.wordpress.org\u002Fnetweblogic\u002F","\u003Cp>WP Safe Mode allows you to view your site temporarily with certain plugins disabled\u002Fenabled as well as switching to another theme.\u003C\u002Fp>\n\u003Cp>This is particularly useful if you are experiencing problems with a specific plugin or theme and need troubleshoot without it affecting the rest of your site visitors.\u003C\u002Fp>\n\u003Cp>Additionally, a loader file can be directly installed via FTP to help you access an inaccessible site due to PHP errors (e.g. blank screens or white screen of death) to help restore it from the admin panel.\u003C\u002Fp>\n\u003Ch4>Main Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Enter Safe Mode for just yourself whilst logged in.\u003C\u002Fli>\n\u003Cli>Enable Safe Mode for the whole site.\u003C\u002Fli>\n\u003Cli>Admin Bar shortcuts for enabling\u002Fdisabling Safe Mode.\u003C\u002Fli>\n\u003Cli>Restrict Safe Mode to certain IP addresses.\u003C\u002Fli>\n\u003Cli>Automatic installation (if file permissions allow).\u003C\u002Fli>\n\u003Cli>Fallback to a default WordPress theme or one of your choice in Safe Mode.\u003C\u002Fli>\n\u003Cli>Prevent or allow Must-Use plugins from loading in Safe-Mode.\u003C\u002Fli>\n\u003Cli>Handy loader file via FTP when your site is completely inaccessible.\u003C\u002Fli>\n\u003Cli>MultiSite Support\n\u003Cul>\n\u003Cli>Network-wide Safe Mode (for just you, or everyone)\u003C\u002Fli>\n\u003Cli>Restrict Network-wide Safe Mode to certain IP address\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>MultiSite Site-Specific Safe Modes\n\u003Cul>\n\u003Cli>Override Network-wide Safe Mode settings for an individual site\u003C\u002Fli>\n\u003Cli>Network Admins can deactivate Network-Active and Must-Use plugins.\u003C\u002Fli>\n\u003Cli>Allow individual site admins from enabling safe mode for their own site.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Data Privacy and GDPR Compliance\u003C\u002Fh4>\n\u003Cp>No personal data is used or stored by this plugin. For those entering user-only mode, a cookie is loaded to identify that user.\u003C\u002Fp>\n","Disable plugins or switch themes for just you or the whole site for debugging, troubleshooting or accessing and restoring a broken website.",24440,86,8,"2025-04-23T09:57:00.000Z","5.2.6",[19,144,145,146,147],"debugging","recovery","safe-mode","troubleshooting","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-safe-mode\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-safe-mode.1.3.zip",{"attackSurface":151,"codeSignals":179,"taintFlows":190,"riskAssessment":191,"analyzedAt":197},{"hooks":152,"ajaxHandlers":175,"restRoutes":176,"shortcodes":177,"cronEvents":178,"entryPointCount":26,"unprotectedCount":26},[153,159,163,168,172],{"type":154,"name":155,"callback":156,"file":157,"line":158},"action","plugins_loaded","setup","debug-mo-translations.php",28,{"type":154,"name":160,"callback":161,"priority":11,"file":157,"line":162},"init","load_translations",29,{"type":164,"name":165,"callback":166,"priority":11,"file":157,"line":167},"filter","override_load_textdomain","log_file_load",52,{"type":154,"name":169,"callback":170,"priority":26,"file":157,"line":171},"in_admin_footer","show",61,{"type":154,"name":173,"callback":170,"priority":26,"file":157,"line":174},"wp_footer",64,[],[],[],[],{"dangerousFunctions":180,"sqlUsage":181,"outputEscaping":183,"fileOperations":26,"externalRequests":26,"nonceChecks":26,"capabilityChecks":61,"bundledLibraries":189},[],{"prepared":26,"raw":26,"locations":182},[],{"escaped":184,"rawEcho":61,"locations":185},14,[186],{"file":157,"line":187,"context":188},213,"raw output",[],[],{"summary":192,"deductions":193},"The 'debug-mo-translations' plugin version 1.3.1 exhibits a generally strong security posture based on the provided static analysis and vulnerability history.  The absence of any identified CVEs and a clean vulnerability history suggest a history of secure development or a lack of targeting.  The code analysis reveals an extremely limited attack surface, with no AJAX handlers, REST API routes, shortcodes, or cron events exposed.  Furthermore, the plugin demonstrates good practices by using prepared statements for all SQL queries and a high percentage of properly escaped output.  The presence of a capability check is also a positive indicator. \n\nDespite the strong positives, there are a few minor areas that, while not immediate critical risks, could be improved for enhanced security.  The data indicates zero nonce checks. While the attack surface is currently zero, if functionality were ever added that involved user interaction without authentication, this would become a significant vulnerability. Similarly, while no external HTTP requests are made, this is a point to monitor as the plugin evolves. The lack of taint analysis results is notable but doesn't necessarily indicate a weakness as much as it may reflect the simplicity of the plugin's operations or limitations of the analysis performed.  Overall, the plugin appears safe to use, but vigilance regarding potential future additions to its attack surface and adherence to best practices like nonce checks for any interactive elements are recommended.",[194],{"reason":195,"points":196},"Missing nonce checks",5,"2026-04-16T12:05:52.752Z",{"wat":199,"direct":204},{"assetPaths":200,"generatorPatterns":201,"scriptPaths":202,"versionParams":203},[],[],[],[],{"cssClasses":205,"htmlComments":206,"htmlAttributes":207,"restEndpoints":208,"jsGlobals":209,"shortcodeOutput":210},[4],[],[],[],[],[],{"error":212,"url":213,"statusCode":214,"statusMessage":215,"message":215},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fdebug-mo-translations\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":196,"versions":217},[218,224,230,237,244],{"version":6,"download_url":25,"svn_tag_url":219,"released_at":27,"has_diff":220,"diff_files_changed":221,"diff_lines":27,"trac_diff_url":222,"vulnerabilities":223,"is_current":212},"https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug-mo-translations\u002Ftags\u002F1.3.1\u002F",false,[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fdebug-mo-translations%2Ftags%2F1.3&new_path=%2Fdebug-mo-translations%2Ftags%2F1.3.1",[],{"version":133,"download_url":225,"svn_tag_url":226,"released_at":27,"has_diff":220,"diff_files_changed":227,"diff_lines":27,"trac_diff_url":228,"vulnerabilities":229,"is_current":220},"https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-mo-translations.1.3.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug-mo-translations\u002Ftags\u002F1.3\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fdebug-mo-translations%2Ftags%2F1.2&new_path=%2Fdebug-mo-translations%2Ftags%2F1.3",[],{"version":231,"download_url":232,"svn_tag_url":233,"released_at":27,"has_diff":220,"diff_files_changed":234,"diff_lines":27,"trac_diff_url":235,"vulnerabilities":236,"is_current":220},"1.2","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-mo-translations.1.2.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug-mo-translations\u002Ftags\u002F1.2\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fdebug-mo-translations%2Ftags%2F1.1&new_path=%2Fdebug-mo-translations%2Ftags%2F1.2",[],{"version":238,"download_url":239,"svn_tag_url":240,"released_at":27,"has_diff":220,"diff_files_changed":241,"diff_lines":27,"trac_diff_url":242,"vulnerabilities":243,"is_current":220},"1.1","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-mo-translations.1.1.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug-mo-translations\u002Ftags\u002F1.1\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fdebug-mo-translations%2Ftags%2F1.0&new_path=%2Fdebug-mo-translations%2Ftags%2F1.1",[],{"version":112,"download_url":245,"svn_tag_url":246,"released_at":27,"has_diff":220,"diff_files_changed":247,"diff_lines":27,"trac_diff_url":27,"vulnerabilities":248,"is_current":220},"https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-mo-translations.1.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug-mo-translations\u002Ftags\u002F1.0\u002F",[],[]]