[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fm6Ros8eMGdLo3cqFficUses2uWfhEGEd5CYbWFrWI0g":3},{"slug":4,"display_name":5,"profile_url":6,"plugin_count":7,"total_installs":8,"avg_security_score":9,"avg_patch_time_days":10,"trust_score":11,"computed_at":12,"plugins":13},"hellofromtonya","Tonya Mork","https:\u002F\u002Fprofiles.wordpress.org\u002Fhellofromtonya\u002F",4,2000320,89,30,86,"2026-04-03T23:03:20.607Z",[14,39,61,80],{"slug":15,"name":16,"version":17,"author":5,"author_profile":6,"description":18,"short_description":19,"active_installs":20,"downloaded":21,"rating":22,"num_ratings":23,"last_updated":24,"tested_up_to":25,"requires_at_least":26,"requires_php":27,"tags":28,"homepage":33,"download_link":34,"security_score":35,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"classic-widgets","Classic Widgets","0.3","\u003Cp>Classic Widgets is an official plugin maintained by the WordPress team that restores the previous (“classic”) WordPress widgets settings screens. It will be supported and maintained to 2024, or as long as is necessary.\u003C\u002Fp>\n\u003Cp>Once activated and when using a classic (non-block) theme, this plugin restores the previous widgets settings screens and disables the block editor from managing widgets. There is no other configuration, the classic widgets settings screens are enabled or disabled by either enabling or disabling this plugin.\u003C\u002Fp>\n","Enables the previous \"classic\" widgets settings screens in Appearance - Widgets and the Customizer. Disables the block editor from managing widgets.",2000000,7214667,98,262,"2025-12-08T10:52:00.000Z","6.9.4","4.9","5.6",[15,29,30,31,32],"disable","disable-gutenberg","editor","gutenberg","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fclassic-widgets\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fclassic-widgets.0.3.zip",100,0,null,"2026-03-15T15:16:48.613Z",{"slug":40,"name":41,"version":42,"author":5,"author_profile":6,"description":43,"short_description":44,"active_installs":45,"downloaded":46,"rating":35,"num_ratings":47,"last_updated":48,"tested_up_to":49,"requires_at_least":50,"requires_php":51,"tags":52,"homepage":58,"download_link":59,"security_score":60,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"cleanup-duplicate-meta","Cleanup Duplicate Meta","1.0.2","\u003Cp>There are times when your database gets filled up with duplicate entries that you may not want.  Cleanup Duplicate Meta allows you to check for any duplicates in either the Post Meta or User Meta tables.  Then if you want to get rid of them, simply click on the Cleanup button and Cleanup Duplicate Meta deletes the duplicates leaving either the first or last meta (you select which).\u003C\u002Fp>\n\u003Cp>The interface is simple and easy to use:\u003C\u002Fp>\n\u003Col>\n\u003Cli>‘Check for Duplicates’ queries the database and then displays all the duplicates found.\u003C\u002Fli>\n\u003Cli>‘Count Duplicates’ counts all the duplicates found in the database (i.e. a total count).\u003C\u002Fli>\n\u003Cli>The ‘Cleanup’ buttons trigger a SQL query to run, which deletes each of the duplicate entries, leaving either the first or last one (per your selection) in the database.  All non-duplicates remain untouched by the plugin.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>See the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fcleanup-duplicate-meta\u002Fscreenshots\u002F\" rel=\"ugc\">screenshots tab\u003C\u002Fa> for more details.\u003C\u002Fp>\n","Cleanup Duplicate Meta gives you a tool to check for and delete duplicate Post and\u002For User Meta entries in the database tables.",200,9629,11,"2015-05-09T11:17:00.000Z","4.2.39","3.5","",[53,54,55,56,57],"database-cleanup","duplicate-meta","meta","post-meta","user-meta","http:\u002F\u002Fwpdevelopersclub.com\u002Fwordpress-plugins\u002Fcleanup-duplicate-meta\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcleanup-duplicate-meta.1.0.2.zip",85,{"slug":62,"name":63,"version":64,"author":5,"author_profile":6,"description":65,"short_description":66,"active_installs":35,"downloaded":67,"rating":35,"num_ratings":68,"last_updated":69,"tested_up_to":70,"requires_at_least":50,"requires_php":71,"tags":72,"homepage":78,"download_link":79,"security_score":60,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"kint-php-debugger","Kint PHP Debugger","2.0.2","\u003Cp>This WordPress plugin is a wrapper for the \u003Ca href=\"https:\u002F\u002Fkint-php.github.io\u002Fkint\u002F\" rel=\"nofollow ugc\">Kint\u003C\u002Fa> PHP Debugger utility version 1.x.  Now instead of using var_dump() or print_r(), you simply use d() with zero, nadda, no formatting required.\u003C\u002Fp>\n\u003Cp>Use this tool when you are debugging your website, in place of \u003Cstrong>\u003Ca href=\"http:\u002F\u002Fphp.net\u002Fmanual\u002Fen\u002Ffunction.var-dump.php\" rel=\"nofollow ugc\">var_dump()\u003C\u002Fa>\u003C\u002Fstrong>, \u003Cstrong>\u003Ca href=\"http:\u002F\u002Fphp.net\u002Fmanual\u002Fen\u002Ffunction.print-r.php\" rel=\"nofollow ugc\">print_r()\u003C\u002Fa>\u003C\u002Fstrong> and \u003Cstrong>\u003Ca href=\"http:\u002F\u002Fphp.net\u002Fmanual\u002Fen\u002Ffunction.debug-backtrace.php\" rel=\"nofollow ugc\">debug_backtrace()\u003C\u002Fa>\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Ch4>Handy Tools\u003C\u002Fh4>\n\u003Cp>Some handy tools just for the PHP Developer:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>d( $var );\u003C\u002Fcode> to render a collapsible UI container which displays your variable data in “the most informative way”\u003C\u002Fli>\n\u003Cli>\u003Ccode>ddd( $var );\u003C\u002Fcode> same as d() except that it also executes \u003Ccode>die()\u003C\u002Fcode> to halt execution.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Here are some variations of \u003Ccode>d()\u003C\u002Fcode> to give you the display you want:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>~d( $var );\u003C\u002Fcode> outputs in plain text format.\u003C\u002Fli>\n\u003Cli>\u003Ccode>+d( $var );\u003C\u002Fcode> disregards depth level limits and outputs everything\u003C\u002Fli>\n\u003Cli>\u003Ccode>!d( $var );\u003C\u002Fcode> shows expanded rich output\u003C\u002Fli>\n\u003Cli>\u003Ccode>-d( $var );\u003C\u002Fcode> attempts to ob_clean() the previous output (dump something inside of HTML)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Profiler\u003C\u002Fh4>\n\u003Cp>Kint even includes a naïve profiler, which can help you analyze which blocks of code take longer than others:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Kint::dump( microtime() ); \u002F\u002F just pass microtime()\nsleep( 1 );\nKint::dump( microtime(), 'after sleep(1)' );\nsleep( 2 );\nddd( microtime(), 'final call, after sleep(2)' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>See \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fkint-php-debugger\u002Fscreenshots\u002F\" rel=\"ugc\">screenshot 2\u003C\u002Fa> for what is rendered out in your browser.\u003C\u002Fp>\n\u003Ch3>Admin Bar\u003C\u002Fh3>\n\u003Cp>“KINT ACTIVE” indicator displays in the WordPress admin bar to alert you when the plugin is active.\u003C\u002Fp>\n","Kint is a modern and powerful PHP debugging helper, which requires zero-setup and replaces var_dump(), print_r() and debug_backtrace().",13073,12,"2019-03-11T17:29:00.000Z","5.1.22","5.3",[73,74,75,76,77],"debug","debugger","kint","print_r","var_dump","https:\u002F\u002Fgithub.com\u002FKnowTheCode\u002Fkint-php-debugger","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fkint-php-debugger.2.0.2.zip",{"slug":81,"name":82,"version":83,"author":5,"author_profile":6,"description":84,"short_description":85,"active_installs":86,"downloaded":87,"rating":35,"num_ratings":88,"last_updated":89,"tested_up_to":70,"requires_at_least":26,"requires_php":27,"tags":90,"homepage":92,"download_link":93,"security_score":60,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"debug-toolkit","Debug Toolkit","1.0.1","\u003Cp>Debug Toolkit makes debugging your code easier and more enjoyable.  It provides you with interactive and helpful tools:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Better PHP error interface from (\u003Ca href=\"http:\u002F\u002Ffilp.github.io\u002Fwhoops\u002F\" rel=\"nofollow ugc\">Whoops\u003C\u002Fa>)\u003C\u002Fli>\n\u003Cli>Better variable inspection – no need to use \u003Ccode>var_dump\u003C\u002Fcode>, \u003Ccode>print_r\u003C\u002Fcode>, or X-debug\u003C\u002Fli>\n\u003Cli>An interactive way to back trace the program’s execution order\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Better PHP Error Interface from Whoops\u003C\u002Fh3>\n\u003Cp>The built-in PHP error container is basic and not as helpful as it could be.  On top of that, it’s rather ugly. Wouldn’t you agree?\u003C\u002Fp>\n\u003Cp>Whoops gives you a cool interface that is helpful, interactive, and quite nice to look at.  Some features:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Provides the error message and links to search Google, DuckDuckGo, and Stack Overflow.\u003C\u002Fli>\n\u003Cli>Shows the actual code where the error occurred.\u003C\u002Fli>\n\u003Cli>Provides an interactive call stack.  Click each and the actual code appears in the viewer panel.\u003C\u002Fli>\n\u003Cli>Environment and details including GET Data, POST Data, Files, Cookie, Session, Server\u002FRequest Data, Environment Variables, and Registered Handlers.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>See the tools in action in this video\u003C\u002Fp>\n\u003Cp>\u003Ciframe loading=\"lazy\" title=\"Introducing the Debug Toolkit Plugin for WordPress\" src=\"https:\u002F\u002Fplayer.vimeo.com\u002Fvideo\u002F322351688?dnt=1&app_id=122963\" width=\"750\" height=\"422\" frameborder=\"0\" allow=\"autoplay; fullscreen; picture-in-picture; clipboard-write\">\u003C\u002Fiframe>\u003C\u002Fp>\n\u003Ch3>Better Variable Inspection\u003C\u002Fh3>\n\u003Cp>Though X-debug is powerful, it can be difficult to set up and run.  For that reason, it’s common to dump or print out the variable to browser.  But the built-in display for the PHP \u003Ccode>var_dump\u003C\u002Fcode> and \u003Ccode>print_r\u003C\u002Fcode> is basic.\u003C\u002Fp>\n\u003Cp>This plugin includes both two very popular variable dumper tools:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fsymfony.com\u002Fdoc\u002Fcurrent\u002Fcomponents\u002Fvar_dumper.html\" rel=\"nofollow ugc\">VarDumper from Symfony\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fkint-php.github.io\u002Fkint\u002F\" rel=\"nofollow ugc\">Kint – a modern and powerful PHP debugging helper\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>VarDumper provides a simple container that displays where you place it.\u003C\u002Fp>\n\u003Cp>On the other hand, Kint provides a more powerful interface that gives you more information such as printing out the expression that was passed into it, the data type, memory size, and the value.\u003C\u002Fp>\n\u003Cp>To make it even easier, the following utility functions are available for you to use in your code:\u003C\u002Fp>\n\u003Ch4>Available Functions for Inspecting Variable Values\u003C\u002Fh4>\n\u003Cp>Let’s explore the functions that are available for you through this plugin.  We’ll use the variable inspectors to dump \u003Ccode>global $post\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>Note: You can pass in any variable or function that returns a value.\u003C\u002Fp>\n\u003Cp>Dumps the given variable(s):\u003C\u002Fp>\n\u003Cpre>\u003Ccode>global $post;\n\n\u002F\u002F VarDumper\nvdump( $post );\n\n\u002F\u002F Kint\ndump( $post );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Dumps the given variable(s) and then exits the program’s execution:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>global $post;\n\n\u002F\u002F VarDumper\nvdump_and_die( $post );\n\n\u002F\u002F Kint\ndump_and_die( $post );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>In addition, there are alias (shorthand) functions available for you if you prefer shorter function names:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>vd()\u003C\u002Fcode> is an alias for \u003Ccode>vdump()\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>vdd()\u003C\u002Fcode> and \u003Ccode>vdd()\u003C\u002Fcode> are aliases for \u003Ccode>vdump_and_die()\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>d()\u003C\u002Fcode> is an alias for \u003Ccode>dump()\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>dd()\u003C\u002Fcode> and \u003Ccode>ddd()\u003C\u002Fcode> are aliases for \u003Ccode>dump_and_die()\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Tracing Call Stack\u003C\u002Fh3>\n\u003Cp>When debugging, there are times when you need to see the order in which functions were called that lead to a certain point in the program.  PHP offers a backtrace that traces back the execution order from the point when the function is invoked.\u003C\u002Fp>\n\u003Cp>To make backtracing easier, this plugin provides you with a \u003Ccode>trace()\u003C\u002Fcode> function and combines it with the variable inspect functions.\u003C\u002Fp>\n\u003Cp>For example, if you wanted to trace the call stack to the start of the loop in your theme’s \u003Ccode>functions.php\u003C\u002Fcode> file, you could use this code:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_action( 'loop_start', function() {\n    trace();\n} );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Available Trace Functions\u003C\u002Fh4>\n\u003Cp>Place these functions at the point where you want to trace the call stack.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>trace();\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>trace_vdump();\u003C\u002Fcode> – Combines \u003Ccode>trace()\u003C\u002Fcode> and \u003Ccode>vdump()\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>trace_dump();\u003C\u002Fcode> – Combines \u003Ccode>trace()\u003C\u002Fcode> and \u003Ccode>dump()\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>trace_vdump_and_die();\u003C\u002Fcode> – Combines \u003Ccode>trace()\u003C\u002Fcode> and \u003Ccode>vdump_and_die()\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>trace_dump_and_die();\u003C\u002Fcode> – Combines \u003Ccode>trace()\u003C\u002Fcode> and \u003Ccode>dump_and_die()\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>In addition, there are alias (shorthand) functions available for you if you prefer shorter function names:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>tracevd();\u003C\u002Fcode> – Combines \u003Ccode>trace()\u003C\u002Fcode> and \u003Ccode>vd()\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>traced();\u003C\u002Fcode> – Combines \u003Ccode>trace()\u003C\u002Fcode> and \u003Ccode>d()\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>tracevdd();\u003C\u002Fcode> – Combines \u003Ccode>trace()\u003C\u002Fcode> and \u003Ccode>vdd()\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>tracedd();\u003C\u002Fcode> – Combines \u003Ccode>trace()\u003C\u002Fcode> and \u003Ccode>dd()\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>tracevddd();\u003C\u002Fcode> – Combines \u003Ccode>trace()\u003C\u002Fcode> and \u003Ccode>vddd()\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>traceddd();\u003C\u002Fcode> – Combines \u003Ccode>trace()\u003C\u002Fcode> and \u003Ccode>ddd()\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Admin Bar\u003C\u002Fh3>\n\u003Cp>“DEBUG ACTIVE” indicator displays in the WordPress admin bar to alert you when the plugin is active.\u003C\u002Fp>\n","Code debug made easier and more enjoyable.",20,8785,13,"2019-03-11T15:34:00.000Z",[91,73,74,76,77],"backtrace","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdebug-toolkit","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-toolkit.1.0.1.zip"]