[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fCfKKUk_6g2Xx2LIf6ekFAUoBmrpOqf9ffiV4U99IQAg":3},{"slug":4,"display_name":4,"profile_url":5,"plugin_count":6,"total_installs":7,"avg_security_score":8,"avg_patch_time_days":9,"trust_score":10,"computed_at":11,"plugins":12},"tombenner","https:\u002F\u002Fprofiles.wordpress.org\u002Ftombenner\u002F",5,70,85,30,84,"2026-04-04T08:30:24.481Z",[13,35,55,72,88],{"slug":14,"name":15,"version":16,"author":4,"author_profile":5,"description":17,"short_description":18,"active_installs":9,"downloaded":19,"rating":20,"num_ratings":20,"last_updated":21,"tested_up_to":22,"requires_at_least":23,"requires_php":24,"tags":25,"homepage":31,"download_link":32,"security_score":8,"vuln_count":20,"unpatched_count":20,"last_vuln_date":33,"fetched_at":34},"registration-statistics","Registration Statistics","1.0","\u003Cp>Registration Statistics is a WordPress plugin that adds a tool in the WordPress admin section that allows administrators to choose a date range and see graphs and tables showing the number of registrations (i.e. new users) that occurred on each day and the number of cumulative registrations on that day (the total number of users who had registered on or before that day).\u003C\u002Fp>\n\u003Cp>The graphs and tables are interactive; you can sort the tables by date or by count, and you can mouse over the graph to see the count at that point.  You can also click on a point on a graph and choose to view a list of posts that were published on that day or during that month, which may allow you to see what posts might’ve caused a peak in registrations (and thus gauge what kinds of posts you can make in the future to spur on more registrations).\u003C\u002Fp>\n\u003Cp>If you’d like to grab development releases, see what new features are being added, or browse the source code please visit the \u003Ca href=\"http:\u002F\u002Fgithub.com\u002Ftombenner\u002Fregistration-statistics\" rel=\"nofollow ugc\">GitHub repo\u003C\u002Fa>.\u003C\u002Fp>\n","Displays graphs and tables showing counts of daily user registrations for a selected date range.",5645,0,"2011-06-04T17:45:00.000Z","3.1.4","3.0","",[26,27,28,29,30],"analytics","registration","statistics","stats","tracking","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fregistration-statistics\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fregistration-statistics.zip",null,"2026-03-15T15:16:48.613Z",{"slug":36,"name":37,"version":38,"author":4,"author_profile":5,"description":39,"short_description":40,"active_installs":41,"downloaded":42,"rating":43,"num_ratings":44,"last_updated":45,"tested_up_to":46,"requires_at_least":23,"requires_php":24,"tags":47,"homepage":53,"download_link":54,"security_score":8,"vuln_count":20,"unpatched_count":20,"last_vuln_date":33,"fetched_at":34},"front-end-users","Front-End Users","1.2.2","\u003Cp>Front-End Users is a WordPress plugin that prevents specified user roles from accessing the WordPress admin section (the pages in \u002Fwp-admin\u002F), sets up a profile editing page on the front-end, and allows for customization of front-end user-specific pages.  This allows you to hide all of the WordPress back-end from specified roles (e.g. Subscribers) and instead present to them a profile editing page (and, optionally, other user-specific pages) that have the same layout as the rest of the site.  The front-end functionality is available to all roles, but you can choose which roles are able to access the WordPress admin section (by default, only Administrators have access to it).\u003C\u002Fp>\n\u003Cp>Front-End Users also makes it easy to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Display user-specific links that depend on the login state (e.g. “Sign in | Register”, “John | Sign out”, “John | Dashboard | Sign out”)\u003C\u002Fli>\n\u003Cli>Change the URL of the profile editing page and other user-specific pages\u003C\u002Fli>\n\u003Cli>Add other user-specific pages and display a menu of all of some of these pages\u003C\u002Fli>\n\u003Cli>Determine whether the current user has access to the admin section\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The documentation for the hooks is in \u003Ca href=\"http:\u002F\u002Fgithub.com\u002Ftombenner\u002Ffront-end-users\u002Fblob\u002Fmaster\u002Fexample_hooks.php\" rel=\"nofollow ugc\">example_hooks.php\u003C\u002Fa>, and the documentation for the functions is in \u003Ca href=\"http:\u002F\u002Fgithub.com\u002Ftombenner\u002Ffront-end-users\u002Fblob\u002Fmaster\u002Ffunctions.php\" rel=\"nofollow ugc\">functions.php\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>If the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fuser-avatar\u002F\" rel=\"ugc\">User Avatar plugin\u003C\u002Fa> is also installed, the avatar-editing functionality it provides will be shown on the front-end user settings page.\u003C\u002Fp>\n\u003Cp>If you’d like to grab development releases, see what new features are being added, or browse the source code please visit the \u003Ca href=\"http:\u002F\u002Fgithub.com\u002Ftombenner\u002Ffront-end-users\" rel=\"nofollow ugc\">GitHub repo\u003C\u002Fa>.\u003C\u002Fp>\n","Hides the WordPress admin section from specified user roles, allows users to edit their settings from the front-end, and more.",10,21621,26,3,"2012-01-04T02:52:00.000Z","3.3.2",[48,49,50,51,52],"admin","front-end","public","roles","users","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Ffront-end-users\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffront-end-users.1.2.2.zip",{"slug":56,"name":57,"version":58,"author":4,"author_profile":5,"description":59,"short_description":60,"active_installs":41,"downloaded":61,"rating":20,"num_ratings":20,"last_updated":62,"tested_up_to":63,"requires_at_least":23,"requires_php":24,"tags":64,"homepage":70,"download_link":71,"security_score":8,"vuln_count":20,"unpatched_count":20,"last_vuln_date":33,"fetched_at":34},"hierarchical-documentation","Hierarchical Documentation","1.1","\u003Cp>Hierarchical Documentation allows admins to create public pages of documentation and organize them hierarchically using a tree listing the pages where each page can be dragged to its desired position. It supports syntax highlighting for blocks of code and \u003Ca href=\"http:\u002F\u002Fdaringfireball.net\u002Fprojects\u002Fmarkdown\u002F\" rel=\"nofollow ugc\">Markdown\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>For an example of Hierarchical Documentation in action, see \u003Ca href=\"http:\u002F\u002Fwpmvc.org\u002F\" rel=\"nofollow ugc\">wpmvc.org\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Please note that the default behavior is to display the documentation page that has an ID of 1 as the site’s homepage. This can be changed by editing the first line of \u003Ccode>hierarchical-documentation\u002Fapp\u002Fconfig\u002Froutes.php\u003C\u002Fcode>. (See the \u003Ca href=\"http:\u002F\u002Fwpmvc.org\u002Fdocumentation\u002F62\u002Frouting\u002F\" rel=\"nofollow ugc\">WP MVC documentation page on routing\u003C\u002Fa> for details.)\u003C\u002Fp>\n\u003Cp>This plugin depends on \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fwp-mvc\u002F\" rel=\"ugc\">WP MVC\u003C\u002Fa>, so that plugin needs to be installed and activated before this one is activated.\u003C\u002Fp>\n\u003Cp>If you’d like to grab development releases, see what new features are being added, or browse the source code please visit the \u003Ca href=\"http:\u002F\u002Fgithub.com\u002Ftombenner\u002Fhierarchical-documentation\" rel=\"nofollow ugc\">GitHub repo\u003C\u002Fa>.\u003C\u002Fp>\n","Lets admins create searchable, hierarchically-organized documentation. Supports Markdown and syntax highlighting for code. Requires WP MVC.",3254,"2012-03-02T22:21:00.000Z","3.2.1",[65,66,67,68,69],"code","codex","documentation","hierarchical","reference","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fhierarchical-documentation\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhierarchical-documentation.1.1.zip",{"slug":73,"name":74,"version":16,"author":4,"author_profile":5,"description":75,"short_description":76,"active_installs":41,"downloaded":77,"rating":10,"num_ratings":6,"last_updated":78,"tested_up_to":46,"requires_at_least":79,"requires_php":24,"tags":80,"homepage":86,"download_link":87,"security_score":8,"vuln_count":20,"unpatched_count":20,"last_vuln_date":33,"fetched_at":34},"mysql-profiler","MySQL Profiler","\u003Cp>MySQL Profiler displays debugging information about SQL queries to admin WordPress users.  For each query, the profiler displays the time, syntax-highlighted SQL, and a trace of the functions (as well as the file and line number that the functions were called from) that were called.\u003C\u002Fp>\n\u003Cp>The list can be sorted by any of its columns, so you can, for example:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Order the list by ID to see the chronological order of the queries\u003C\u002Fli>\n\u003Cli>Order the list by time to see the slowest queries\u003C\u002Fli>\n\u003Cli>Order the list by query to group the queries by type (SELECT, UPDATE, etc)\u003C\u002Fli>\n\u003Cli>Order the list by trace to group the queries by similar origins\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The list can also filtered by typing in the search box, so you can, for example:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>View all queries that use the wp_posts table\u003C\u002Fli>\n\u003Cli>View all queries that are related to the use of a function in taxonomy.php\u003C\u002Fli>\n\u003Cli>View all queries that are related to the use of a specific function or class\u003C\u002Fli>\n\u003Cli>View all queries that call a specific MySQL function\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>To turn off syntax highlighting, put the following in wp-config.php:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define('MP_HIGHLIGHT_SYNTAX', false);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>To omit the file and line number from the function trace and display the functions as a comma-separated list (to save vertical space), define the following in wp-config.php:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define('MP_DISPLAY_FILES', false);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>This plugin was loosely based on \u003Ca href=\"http:\u002F\u002Fbueltge.de\u002F\" rel=\"nofollow ugc\">Frank Bueltge\u003C\u002Fa>‘s \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fdebug-queries\u002F\" rel=\"ugc\">Debug Queries\u003C\u002Fa> plugin, so a hearty thanks to him for the development of that.\u003C\u002Fp>\n\u003Cp>If you’d like to grab development releases, see what new features are being added, or browse the source code please visit\u002Ffollow the \u003Ca href=\"http:\u002F\u002Fgithub.com\u002Ftombenner\u002Fmysql-profiler\" rel=\"nofollow ugc\">GitHub repo\u003C\u002Fa>.\u003C\u002Fp>\n","Displays a list of each page's SQL queries and the functions calling them that can be searched and sorted by time, type, etc.",6999,"2012-03-06T20:16:00.000Z","2.9",[81,82,83,84,85],"debug","debugging","mysql","profiler","profiling","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fmysql-profiler\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmysql-profiler.1.0.zip",{"slug":89,"name":90,"version":16,"author":4,"author_profile":5,"description":91,"short_description":92,"active_installs":41,"downloaded":93,"rating":20,"num_ratings":20,"last_updated":94,"tested_up_to":46,"requires_at_least":23,"requires_php":24,"tags":95,"homepage":101,"download_link":102,"security_score":8,"vuln_count":20,"unpatched_count":20,"last_vuln_date":33,"fetched_at":34},"wp-coffeescript","WP CoffeeScript","\u003Cp>WP CoffeeScript is a WordPress plugin that makes enqueueing \u003Ca href=\"http:\u002F\u002Fcoffeescript.org\" rel=\"nofollow ugc\">CoffeeScript\u003C\u002Fa> as easy as enqueueing JavaScript.  Instead of using \u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FFunction_Reference\u002Fwp_enqueue_script\" rel=\"nofollow ugc\">\u003Ccode>wp_enqueue_script()\u003C\u002Fcode>\u003C\u002Fa>, as you would for JS, you just use \u003Ccode>enqueue_coffeescript()\u003C\u002Fcode>, which takes almost exactly the same arguments.  The only difference is that the second argument should be the file path instead of the URL.  If you’d like to compile multiple CS files into a single JS file, you can use an array of file paths as the second argument.\u003C\u002Fp>\n\u003Cp>Please note that the \u003Ca href=\"http:\u002F\u002Fcoffeescript.org\u002F#installation\" rel=\"nofollow ugc\">CoffeeScript executable\u003C\u002Fa> must be installed on the server.  You can also set a custom path to the executable (see the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Ftombenner\u002Fwp-coffeescript\" rel=\"nofollow ugc\">examples\u003C\u002Fa>).\u003C\u002Fp>\n\u003Cp>If you’d like to grab development releases, see what new features are being added, or browse the source code please visit the \u003Ca href=\"http:\u002F\u002Fgithub.com\u002Ftombenner\u002Fwp-coffeescript\" rel=\"nofollow ugc\">GitHub repo\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Examples\u003C\u002Fh3>\n\u003Cp>Enqueue a CoffeeScript file that’s in the theme directory:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>enqueue_coffeescript('my-handle', get_template_directory().'\u002Fmy-script.coffee');\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Enqueue multiple CS files, compiling them into a single output file:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$script1 = get_template_directory().'\u002Fscript1.coffee';\n$script2 = get_template_directory().'\u002Fscript2.coffee';\nenqueue_coffeescript('my-handle', array($script1, $script2));\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Enqueue a CS file in the footer with dependencies (the arguments are exactly the same as in \u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FFunction_Reference\u002Fwp_enqueue_script\" rel=\"nofollow ugc\">\u003Ccode>wp_enqueue_script()\u003C\u002Fcode>\u003C\u002Fa>):\u003C\u002Fp>\n\u003Cpre>\u003Ccode>enqueue_coffeescript('my-handle', get_template_directory().'\u002Fmy-script.coffee', array('dep1', 'dep2'), false, true);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Set a custom path to the CS executable (the default value is \u003Ccode>coffeescript\u003C\u002Fcode>):\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_filter('wpcs_executable', 'set_wpcs_executable');\nfunction set_wpcs_executable($path) {\n    return '\u002Fmy\u002Fpath\u002Fto\u002Fcoffeescript';\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Compile the CS on every page load (the default behavior is to only compile when the JS has been modified):\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_filter('wpcs_caching_enabled', 'disable_wpcs_caching');\nfunction disable_wpcs_caching($is_enabled) {\n    return false;\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n","Allows developers to easily use CoffeeScript in WordPress. Simply use enqueue_coffeescript(); the compilation is done automatically behind the scenes.",1629,"2012-01-09T20:51:00.000Z",[96,97,98,99,100],"coffeescript","cs","development","javascript","js","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fwp-coffeescript\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-coffeescript.1.0.zip"]