[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fz6AvzldoZ5VhUsTKL_PD-Uo0y-spwqH_f_vEPJfGYqo":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":14,"tags":17,"homepage":22,"download_link":23,"security_score":24,"vuln_count":13,"unpatched_count":13,"last_vuln_date":25,"fetched_at":26,"vulnerabilities":27,"developer":28,"crawl_stats":25,"alternatives":36,"analysis":139,"fingerprints":213},"wp-debug-logger","WP Debug Logger","0.1","Donncha O Caoimh (a11n)","https:\u002F\u002Fprofiles.wordpress.org\u002Fdonncha\u002F","\u003Cp>This plugin logs the activity of supported plugins to a file, making it easier to figure out why there’s a problem.\u003C\u002Fp>\n\u003Cp>If you have been asked to install this plugin because of a support issue then installing this plugin is just like installing any other plugin. Once installed, go to Settings->WP Logger and enable logging. If you have a number of supported plugins enable the one you are interested in.\u003C\u002Fp>\n\u003Cp>Developers who want to use this plugin to add logging to their own plugin should see the Developers section of this documentation.\u003C\u002Fp>\n\u003Cp>Mark Jaquith’s \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fmonitor-pages\u002F\" rel=\"ugc\">Monitor Pages\u003C\u002Fa> plugin was used as a template for this plugin. Thanks Mark!\u003C\u002Fp>\n\u003Ch4>Developers\u003C\u002Fh4>\n\u003Cp>Other plugins can use this plugin to record important events which are then dumped to a log file. Plugins must add the event to a global array in the following way:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$GLOBALS[ 'wp_log' ][ 'name_of_plugin' ][] = 'Some important event';\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Plugins must also add themselves to a list of enabled plugins. This will make it easier for blog owners to filter out which plugin they want to debug on the settings page. Add and edit the following code so it is executed when the plugin is loaded.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$GLOBALS[ 'wp_log_plugins' ][] = 'name_of_plugin';\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>A hypothetical example might be a plugin (let’s call it “Big A”) that uses the output buffer to change the letter “a” to “A”. The events recorded by this might include the following:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$GLOBALS[ 'wp_log' ][ 'big_a' ][] = 'Created output buffer';\n$GLOBALS[ 'wp_log' ][ 'big_a' ][] = 'Output buffer callback';\n$GLOBALS[ 'wp_log' ][ 'big_a' ][] = 'Replaced a with A in page';\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>This plugin takes the “wp_log” array and dumps it to a file in the upload directory of the blog it’s activated on. The file is linked from the plugin settings page and can be deleted on that page too. The file is a simple text file and is not protected in any way so be careful if auth cookies are logged by a plugin.\u003C\u002Fp>\n\u003Cp>A “log” function isn’t included but if you want to add one to your plugin check the constant WP_DEBUG_LOG is defined before adding to the log array. If your plugin doesn’t use a class make sure that you call the log function a unique name so it doesn’t conflict with other plugins.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>function log( $message ) {\n    if ( defined( 'WP_DEBUG_LOG' ) )\n        $GLOBALS[ 'wp_log' ][ 'name_of_plugin' ][] = $message;\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n","A plugin that makes it easy to log code activity to a file.",10,4742,0,"","4.7.32","2.9.2",[18,19,20,21],"debug","development","log","php","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fwp-debug-logger\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-debug-logger.zip",100,null,"2026-03-15T10:48:56.248Z",[],{"slug":29,"display_name":7,"profile_url":8,"plugin_count":30,"total_installs":31,"avg_security_score":32,"avg_patch_time_days":33,"trust_score":34,"computed_at":35},"donncha",12,31620,91,4657,73,"2026-04-04T14:37:51.546Z",[37,59,76,101,120],{"slug":38,"name":39,"version":40,"author":41,"author_profile":42,"description":43,"short_description":44,"active_installs":45,"downloaded":46,"rating":24,"num_ratings":47,"last_updated":48,"tested_up_to":49,"requires_at_least":50,"requires_php":51,"tags":52,"homepage":55,"download_link":56,"security_score":57,"vuln_count":13,"unpatched_count":13,"last_vuln_date":25,"fetched_at":58},"php-console-log","PHP Console Log","1.0.1","Marcus Viar","https:\u002F\u002Fprofiles.wordpress.org\u002Fmarcusviar\u002F","\u003Ch4>Examples\u003C\u002Fh4>\n\u003Cp>Place the \u003Cstrong>do_action( ‘php_console_log’, ‘My String or Array’ );\u003C\u002Fstrong> function anywhere in your WordPress plugin PHP code. The value(s) you pass into \u003Cstrong>do_action( ‘php_console_log’, ‘My String or Array’ );\u003C\u002Fstrong> will be logged to the web console in your browser.\u003C\u002Fp>\n\u003Ch4>Pass in a string\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>$my_string = 'My String';\ndo_action( 'php_console_log', $my_string );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Pass in an array\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>$my_array = array(\n    'elm 1'\n    'elm 2',\n);\ndo_action( 'php_console_log', $my_array );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Pass in an associative array\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>$my_array = array(\n    'key 1'=>'elm 1',\n    'key 2'=>'elm 2',\n);\ndo_action( 'php_console_log', $my_array);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Pass in an unlimited number of arguments nested to an unlimited depth (multi-dimensional array)\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>$my_array = array(\n    'My String 1',\n    'My String 2',\n    array(\n        'elm 1',\n        'elm 2',\n    ),\n    'My String 3',\n    array(\n        'key 1'=>'elm 1',\n        'key 2'=>'elm 2',\n        'key 3' => array(\n            'key 3a' => 'elm 3a',\n            'key 3b' => 'elm 3b',\n        ),\n    ),\n    'My String 4'\n);\ndo_action( 'php_console_log', $my_array);\n\u003C\u002Fcode>\u003C\u002Fpre>\n","Log PHP variables and arrays to the web console in your browser via JavaScript's console.log(). No browser extensions required.",20,2536,1,"2020-02-07T08:58:00.000Z","5.3.21","4.4","5.6.20",[53,54,18,19,21],"browser","console-log","https:\u002F\u002Fmarcusviar.com\u002Fphp-console-log","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fphp-console-log.1.0.1.zip",85,"2026-03-15T15:16:48.613Z",{"slug":60,"name":61,"version":62,"author":63,"author_profile":64,"description":65,"short_description":66,"active_installs":13,"downloaded":67,"rating":13,"num_ratings":13,"last_updated":68,"tested_up_to":69,"requires_at_least":70,"requires_php":71,"tags":72,"homepage":14,"download_link":75,"security_score":24,"vuln_count":13,"unpatched_count":13,"last_vuln_date":25,"fetched_at":58},"echo-out-viewer","Echo Out Viewer","4.0.1","aminul Islam","https:\u002F\u002Fprofiles.wordpress.org\u002Faminul147471\u002F","\u003Cp>Echo Out Viewer lets you easily display and inspect PHP variable output directly in the browser, using a console-like interface. Helpful for debugging and development.\u003C\u002Fp>\n","Short Description: A simple tool to output and inspect PHP variables directly in your browser for debugging purposes.",444,"2025-07-21T03:10:00.000Z","6.8.5","5.0","7.0",[18,19,73,74,21],"logging","output","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fecho-out-viewer.zip",{"slug":77,"name":78,"version":79,"author":80,"author_profile":81,"description":82,"short_description":83,"active_installs":84,"downloaded":85,"rating":86,"num_ratings":87,"last_updated":88,"tested_up_to":89,"requires_at_least":90,"requires_php":14,"tags":91,"homepage":96,"download_link":97,"security_score":98,"vuln_count":99,"unpatched_count":13,"last_vuln_date":100,"fetched_at":58},"error-log-viewer","Error Log Viewer by BestWebSoft","1.1.8","bestwebsoft","https:\u002F\u002Fprofiles.wordpress.org\u002Fbestwebsoft\u002F","\u003Cp>Simple utility plugin that helps to find and view log files with errors right from your WordPress admin dashboard. Get access to all your log files from one place. View the latest activity, select logs by date, or view a full log file. Get email notifications about log changes.\u003C\u002Fp>\n\u003Cp>Get access to your website logs and troubleshoot issues faster!\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fbestwebsoft.com\u002Fdemo-error-log-viewer\u002F?ref=readme\" rel=\"nofollow ugc\">View Demo\u003C\u002Fa>\u003C\u002Fp>\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\u002F8LR0F4GgXhM?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>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Enable WordPress error logging with:\n\u003Cul>\n\u003Cli>.htaccess\u003C\u002Fli>\n\u003Cli>wp-config.php using \u003Ccode>inl_set\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>wp-config.php using \u003Ccode>WP_DEBUG\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Search and view error logs:\n\u003Cul>\n\u003Cli>PHP\u003C\u002Fli>\n\u003Cli>WordPress\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Configure email notifications about log changes:\n\u003Cul>\n\u003Cli>Set the email\u003C\u002Fli>\n\u003Cli>Change frequency\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Configure log monitor settings:\n\u003Cul>\n\u003Cli>Choose the log to be displayed\u003C\u002Fli>\n\u003Cli>Choose what to show in the log:\n\u003Cul>\n\u003Cli>Certain last lines in the file\u003C\u002Fli>\n\u003Cli>Log for a certain period of time\u003C\u002Fli>\n\u003Cli>Full file\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>View or save the part of PHP error logs as TXT file\u003C\u002Fli>\n\u003Cli>Compatible with latest WordPress version\u003C\u002Fli>\n\u003Cli>Incredibly simple settings for fast setup without modifying code\u003C\u002Fli>\n\u003Cli>Detailed step-by-step documentation and videos\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If you have a feature suggestion or idea you’d like to see in the plugin, we’d love to hear about it! \u003Ca href=\"https:\u002F\u002Fsupport.bestwebsoft.com\u002Fhc\u002Fen-us\u002Frequests\u002Fnew\" rel=\"nofollow ugc\">Suggest a Feature\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch4>Documentation & Videos\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbestwebsoft.com\u002Fdocumentation\u002Ferror-log-viewer\u002Ferror-log-viewer-user-guide\u002F\" rel=\"nofollow ugc\">[Doc] User Guide\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbestwebsoft.com\u002Fdocumentation\u002Fhow-to-install-a-wordpress-product\u002Fhow-to-install-a-wordpress-plugin\u002F\" rel=\"nofollow ugc\">[Doc] Installation\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Help & Support\u003C\u002Fh4>\n\u003Cp>Visit our Help Center if you have any questions, our friendly Support Team is happy to help – \u003Ca href=\"https:\u002F\u002Fsupport.bestwebsoft.com\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fsupport.bestwebsoft.com\u002F\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch4>Affiliate Program\u003C\u002Fh4>\n\u003Cp>Earn 20% commission by selling the premium WordPress plugins and themes by BestWebSoft — https:\u002F\u002Fbestwebsoft.com\u002Faffiliate\u002F\u003C\u002Fp>\n\u003Ch4>Translation\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Russian (ru_RU)\u003C\u002Fli>\n\u003Cli>Ukrainian (uk)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Some of these translations are not complete. We are constantly adding new features which should be translated. If you would like to create your own language pack or update the existing one, you can send \u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FTranslating_WordPress\" rel=\"nofollow ugc\">the text of PO and MO files\u003C\u002Fa> to \u003Ca href=\"https:\u002F\u002Fsupport.bestwebsoft.com\u002Fhc\u002Fen-us\u002Frequests\u002Fnew\" rel=\"nofollow ugc\">BestWebSoft\u003C\u002Fa> and we’ll add it to the plugin. You can download the latest version of the program for work with PO and MO \u003Ca href=\"https:\u002F\u002Fwww.poedit.net\u002Fdownload.php\" rel=\"nofollow ugc\">files Poedit\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Recommended Plugins\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbestwebsoft.com\u002Fproducts\u002Fwordpress\u002Fplugins\u002Fupdater\u002F?k=e2d89a7eca0a903ab58d99e7ffa3b510\" rel=\"nofollow ugc\">Updater\u003C\u002Fa> – Automatically check and update WordPress website core with all installed plugins and themes to the latest versions.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Credits\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>This plugin incorporates a license verification mechanism to ensure the authenticity of your license key and provide access to premium features and updates. The verification process involves connecting securely to our external service hosted at BestWebSoft website \u003Ca href=\"https:\u002F\u002Fbestwebsoft.com\" rel=\"nofollow ugc\">https:\u002F\u002Fbestwebsoft.com\u003C\u002Fa>. Privacy Policy \u003Ca href=\"https:\u002F\u002Fbestwebsoft.com\u002Fprivacy-policy\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fbestwebsoft.com\u002Fprivacy-policy\u002F\u003C\u002Fa>. End user license agreement \u003Ca href=\"https:\u002F\u002Fbestwebsoft.com\u002Fend-user-license-agreement\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fbestwebsoft.com\u002Fend-user-license-agreement\u002F\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n","Get latest error log messages to diagnose website problems. Define and fix issues faster.",6000,94418,96,9,"2025-12-03T11:15:00.000Z","6.9.4","6.2",[92,93,94,77,95],"add-debug-tool","debug-tool","error-log","php-error-log","https:\u002F\u002Fbestwebsoft.com\u002Fproducts\u002Fwordpress\u002Fplugins\u002Ferror-log-viewer\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ferror-log-viewer.1.1.8.zip",92,5,"2025-10-10 20:39:18",{"slug":102,"name":103,"version":104,"author":105,"author_profile":106,"description":107,"short_description":108,"active_installs":109,"downloaded":110,"rating":86,"num_ratings":111,"last_updated":112,"tested_up_to":113,"requires_at_least":114,"requires_php":14,"tags":115,"homepage":118,"download_link":119,"security_score":57,"vuln_count":13,"unpatched_count":13,"last_vuln_date":25,"fetched_at":58},"bugfu-console-debugger","BugFu Console Debugger","1.3.0","Federico Andrioli","https:\u002F\u002Fprofiles.wordpress.org\u002Ffedeandri\u002F","\u003Cp>Log\u002FDebug the PHP code in your Theme\u002FPlugin with your Browser Console (no extension needed). Made for themes and plugins developers.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>HOW TO CHECK IF BUGFU IS WORKING\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Open your Browser Console, if you see this header, BugFu is working properly\u003C\u002Fp>\n\u003Cpre>\u003Ccode>################################\n#### BugFu Console Debugger ####\n################################\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>HOW TO OPEN YOUR BROWSER JAVASCRIPT CONSOLE\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>If you’ve never used the Browser JavaScript Console before, here’s how you open it:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Chrome PC shift+ctrl+j – Chrome Mac alt+cmd+j\u003C\u002Fli>\n\u003Cli>Firefox PC shift+ctrl+k – Firefox Mac alt+cmd+k\u003C\u002Fli>\n\u003Cli>Safari PC shift+ctrl+c – Safari Mac alt+cmd+c\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>HOW TO USE BUGFU WITH WORDPRESS\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Call the log static method from wherever you are within the WordPress PHP code\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003C?php \u002F* WORDPRESS CODE HERE *\u002F\n\n\u002F* Call it with no arguments to only output some backtrace info *\u002F\nBugFu::log();\n\n\u002F* Call it with a string argument to output that string content *\u002F\nBugFu::log($my_string_content);\n\n\u002F* Call it with a non-string argument to output the structured\n   representation of that argument - it uses var_export() *\u002F\nBugFu::log($my_object-array-variable);\n\n\u002F* Call it with the second optional argument set to \"false\"\n   to turn off the backtrace info (which is on by default) *\u002F\nBugFu::log($my_content, false);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>DEVELOPERS\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Official Github repository:\u003Cbr \u002F>\nhttps:\u002F\u002Fgithub.com\u002Ffedeandri\u002Fbugfu-console-debugger\u003C\u002Fp>\n","Log\u002FDebug the PHP code in your Theme\u002FPlugin with your Browser Console (no extension needed)",300,10184,17,"2023-01-17T15:02:00.000Z","6.1.10","3.8",[18,116,117,20,21],"debug-bar","error","https:\u002F\u002Fgithub.com\u002Ffedeandri\u002Fbugfu-console-debugger","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fbugfu-console-debugger.1.3.zip",{"slug":121,"name":122,"version":123,"author":124,"author_profile":125,"description":126,"short_description":127,"active_installs":128,"downloaded":129,"rating":24,"num_ratings":47,"last_updated":130,"tested_up_to":89,"requires_at_least":90,"requires_php":131,"tags":132,"homepage":14,"download_link":138,"security_score":24,"vuln_count":13,"unpatched_count":13,"last_vuln_date":25,"fetched_at":58},"debug-log-tool","BugTrace – Debug Log Tool","1.0.7","Nikhil G","https:\u002F\u002Fprofiles.wordpress.org\u002Fnsgawli\u002F","\u003Cp>Tired of cumbersome debugging processes? BugTrace – Debug Log Tool streamlines WordPress troubleshooting, providing developers and site administrators with a powerful yet minimalist interface to diagnose and resolve issues swiftly. Stop wasting time with manual wp-config.php edits or FTP access for basic debugging tasks.\u003C\u002Fp>\n\u003Cp>With BugTrace, you can:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Instantly Control Debug Constants:\u003C\u002Fstrong> Gain immediate access to toggle crucial WordPress debugging constants like WP_DEBUG, WP_DEBUG_LOG, WP_DEBUG_DISPLAY, and SCRIPT_DEBUG directly from your dashboard. Activate or deactivate them with a single click—no code editing required, saving you valuable development time and reducing the risk of site-breaking syntax errors.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>AI-Powered Error Resolution (ChatGPT, Gemini & Google):\u003C\u002Fstrong> Stop guessing and start solving! For every log entry, BugTrace provides one-click ‘Help’ links. Instantly send the error message to ChatGPT, Gemini, or Google to find solutions, code snippets, and explanations. Drastically reduce your troubleshooting time and solve complex problems faster than ever before.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Effortlessly Access Debug Logs:\u003C\u002Fstrong> View and download your WordPress \u003Ccode>debug.log\u003C\u002Fcode> file directly from the admin panel. This allows for quick identification of PHP errors, warnings, and notices, helping you pinpoint the source of problems much faster than traditional methods.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Dynamic Log Viewing with Auto & Manual Refresh:\u003C\u002Fstrong> Keep an eye on your \u003Ccode>debug.log\u003C\u002Fcode> in near real-time with the auto-refresh option, or manually refresh the log view whenever you need. This helps in actively monitoring errors as they occur and is invaluable for live debugging sessions.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Securely Inspect Server Configurations:\u003C\u002Fstrong> Safely view the contents of vital server files such as \u003Ccode>.htaccess\u003C\u002Fcode> and wp-config.php (read-only), and review detailed \u003Ccode>phpinfo()\u003C\u002Fcode> output without ever leaving your WordPress environment. This provides essential insights for advanced WordPress troubleshooting and server diagnostics.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Monitor Key System Behaviors:\u003C\u002Fstrong> Get a clear overview of your database table information (including size and row count), view active browser cookies (read-only), inspect WordPress transients (read-only), and check your list of scheduled WordPress cron jobs. This comprehensive visibility helps you understand your site’s inner workings.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Utilize Admin Bar Shortcuts:\u003C\u002Fstrong> Speed up your debugging workflow with convenient admin bar shortcuts to view, download, and clear the \u003Ccode>debug.log\u003C\u002Fcode> file from anywhere in your WordPress admin area.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Quick Log to Clipboard:\u003C\u002Fstrong> Instantly copy the entire contents of your log to your clipboard with a single click. Perfect for quickly sharing log details with support teams, pasting into development tools, or for your own records.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Enjoy a Minimalist Interface:\u003C\u002Fstrong> BugTrace is intentionally lightweight with a clean UI, focusing purely on essential debugging tools to ensure it doesn’t bog down your WordPress site.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Whether you’re developing a new theme or plugin, troubleshooting a tricky bug on a staging server, or performing routine site health checks, BugTrace – Debug Log Tool provides the critical information you need, efficiently and effectively.\u003C\u002Fp>\n","Essential WordPress debug tool: View\u002Fdownload logs, toggle debug settings & inspect server info. Troubleshoot PHP errors & site issues faster!",40,887,"2025-12-07T12:40:00.000Z","7.4",[133,134,135,136,137],"database-info","debug-log","php-errors","troubleshooting-tool","wordpress-debug","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-log-tool.1.0.7.zip",{"attackSurface":140,"codeSignals":162,"taintFlows":179,"riskAssessment":206,"analyzedAt":212},{"hooks":141,"ajaxHandlers":158,"restRoutes":159,"shortcodes":160,"cronEvents":161,"entryPointCount":13,"unprotectedCount":13},[142,147,150,154],{"type":143,"name":144,"callback":144,"file":145,"line":146},"action","init","wp-debug-logger.php",23,{"type":143,"name":148,"callback":148,"file":145,"line":149},"admin_menu",35,{"type":143,"name":151,"callback":152,"file":145,"line":153},"wp-debug-logger-notices","updated",69,{"type":143,"name":155,"callback":156,"file":145,"line":157},"shutdown","wp_log_everything",168,[],[],[],[],{"dangerousFunctions":163,"sqlUsage":164,"outputEscaping":166,"fileOperations":47,"externalRequests":13,"nonceChecks":177,"capabilityChecks":13,"bundledLibraries":178},[],{"prepared":13,"raw":13,"locations":165},[],{"escaped":167,"rawEcho":167,"locations":168},4,[169,172,174,176],{"file":145,"line":170,"context":171},77,"raw output",{"file":145,"line":173,"context":171},80,{"file":145,"line":175,"context":171},109,{"file":145,"line":175,"context":171},2,[],[180,198],{"entryPoint":181,"graph":182,"unsanitizedCount":13,"severity":197},"load_admin (wp-debug-logger.php:46)",{"nodes":183,"edges":194},[184,189],{"id":185,"type":186,"label":187,"file":145,"line":188},"n0","source","$_POST[?] (x2)",61,{"id":190,"type":191,"label":192,"file":145,"line":188,"wp_function":193},"n1","sink","update_option() [Settings Manipulation]","update_option",[195],{"from":185,"to":190,"sanitized":196},true,"low",{"entryPoint":199,"graph":200,"unsanitizedCount":13,"severity":197},"\u003Cwp-debug-logger> (wp-debug-logger.php:0)",{"nodes":201,"edges":204},[202,203],{"id":185,"type":186,"label":187,"file":145,"line":188},{"id":190,"type":191,"label":192,"file":145,"line":188,"wp_function":193},[205],{"from":185,"to":190,"sanitized":196},{"summary":207,"deductions":208},"The wp-debug-logger v0.1 plugin exhibits a generally good security posture based on the static analysis.  The absence of any AJAX handlers, REST API routes, shortcodes, or cron events significantly limits the attack surface. Furthermore, the code shows positive signs with the use of prepared statements for all SQL queries and the presence of nonce checks. The lack of known CVEs and a clean vulnerability history further bolster its perceived security.\n\nHowever, there are areas that warrant attention.  A significant portion (50%) of the plugin's outputs are not properly escaped, creating a potential risk for Cross-Site Scripting (XSS) vulnerabilities.  While taint analysis did not reveal any critical or high-severity issues, the unescaped outputs could still be exploited if user-supplied data is directly included in the output without proper sanitization.  The single file operation is also a point to monitor, though without further context, its risk is unclear.  The absence of capability checks on potential entry points, if any were present, would also be a concern, but the current analysis indicates zero entry points.\n\nIn conclusion, the plugin is currently in a relatively secure state due to its limited attack surface and responsible SQL handling. The primary weakness lies in output escaping, which requires immediate attention to mitigate XSS risks.  The vulnerability history is a positive indicator, suggesting a history of secure development, but proactive security practices, especially regarding output sanitization, remain crucial.",[209],{"reason":210,"points":211},"50% of outputs not properly escaped",6,"2026-03-16T23:20:00.571Z",{"wat":214,"direct":219},{"assetPaths":215,"generatorPatterns":216,"scriptPaths":217,"versionParams":218},[],[],[],[],{"cssClasses":220,"htmlComments":221,"htmlAttributes":222,"restEndpoints":229,"jsGlobals":230,"shortcodeOutput":234},[],[],[223,224,225,226,227,228],"id=\"wp-debug-logger-enabled\"","name=\"wp_debug_logger_enabled\"","id=\"wp_log_plugins\"","name=\"wp_debug_logger_plugins[]\"","id=\"wp-debug-logger-ip\"","name=\"wp_debug_logger_ip\"",[],[231,232,233],"wp_log_settings","wp_log_plugins","wp_log",[]]