[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f_I5LDUvuaB5Tc51W8F2-j90zmGThbyvclnkWOlLeQ5k":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},"dmchale","Dave McHale","https:\u002F\u002Fprofiles.wordpress.org\u002Fdmchale\u002F",5,90130,85,30,84,"2026-05-19T21:15:13.258Z",[14,39,58,78,97],{"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":34,"download_link":35,"security_score":9,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"disable-json-api","Disable REST API","1.8","\u003Cp>The most comprehensive plugin for controlling access to the WordPress REST API!\u003C\u002Fp>\n\u003Cp>Works as a “set it and forget it” install. Just upload and activate, and the entire REST API will be inaccessible to your general site visitors.\u003C\u002Fp>\n\u003Cp>But if you do need to grant access to some endpoints, you can do that too. Go to the Settings page and you can quickly whitelist individual endpoints (or entire branches of endpoints) in the REST API.\u003C\u002Fp>\n\u003Cp>You can even do this on a per-user-role basis, so your unauthenticated users have one set of rules while WooCommerce customers have another while Subscribers and Editors and Admins all have their own. NOTE: Out of the box, all defined user roles will still be granted full access to the REST API until you choose to manage those settings.\u003C\u002Fp>\n\u003Cp>For most versions of WordPress, this plugin will return an authentication error if a user is not allowed to access an endpoint. For legacy support, WordPress 4.4, 4.5, and 4.6 use the provided \u003Ccode>rest_enabled\u003C\u002Fcode> filter to disable the entire REST API.\u003C\u002Fp>\n","Disable the use of the REST API on your website to site users. Now with User Role support!",90000,758515,96,38,"2023-09-14T00:26:00.000Z","6.3.8","4.9","5.6",[29,30,31,32,33],"admin","api","json","rest","rest-api","http:\u002F\u002Fwww.binarytemplar.com\u002Fdisable-json-api","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdisable-json-api.zip",0,null,"2026-04-16T10:56:18.058Z",{"slug":40,"name":41,"version":42,"author":5,"author_profile":6,"description":43,"short_description":44,"active_installs":45,"downloaded":46,"rating":36,"num_ratings":36,"last_updated":47,"tested_up_to":48,"requires_at_least":49,"requires_php":50,"tags":51,"homepage":56,"download_link":57,"security_score":9,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"fake-login-area","Fake Login Area","1.05","\u003Cp>Do you want your organization to appear bigger, or more important\u002Flegitimate\u002Festablished than you are right now?\u003Cbr \u002F>\nThe presence of a user login area on your website will help you achieve that effect for your site visitors.\u003C\u002Fp>\n\u003Cp>After installing this plugin, simply add the class “flaform” to the desired link. When the user clicks the link, a\u003Cbr \u002F>\nmodal window will appear with a user\u002Fpassword prompt to log in. Of course, the form does nothing and will always claim\u003Cbr \u002F>\nto “fail” the login, but it still makes it look like you have more to offer!\u003C\u002Fp>\n\u003Cp>Huge props to \u003Ca href=\"http:\u002F\u002Ft4t5.github.io\u002Fsweetalert\u002F\" rel=\"nofollow ugc\">SweetAlert\u003C\u002Fa>, the awesome popup window that I am using with this\u003Cbr \u002F>\nplugin.\u003C\u002Fp>\n","Allows you to display a user login form to nowhere.",60,3616,"2016-12-08T19:10:00.000Z","4.7.33","2.6","",[52,53,54,55],"login","login-area","user-login","users","http:\u002F\u002Fwww.binarytemplar.com\u002Fplugins\u002Ffake-login-area","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffake-login-area.1.05.zip",{"slug":59,"name":60,"version":61,"author":5,"author_profile":6,"description":62,"short_description":63,"active_installs":64,"downloaded":65,"rating":66,"num_ratings":67,"last_updated":68,"tested_up_to":69,"requires_at_least":70,"requires_php":71,"tags":72,"homepage":76,"download_link":77,"security_score":9,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"google-404","404 Widget for Google","2.1","\u003Cp>\u003Cstrong>– This plugin has been adopted! Please review the description below. –\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>A 404 page is what a user sees when they try to reach a non-existent page on your site (because they’ve clicked on a broken link, the page has been deleted or they’ve mistyped a URL).\u003C\u002Fp>\n\u003Cp>While the standard 404 page can vary depending on your web host, it doesn’t usually provide the user with much useful information and users may just surf away from your site. Therefore, Google recommend creating a custom 404 page that provides the user with more information about your site and its content.\u003C\u002Fp>\n\u003Cp>The Google 404 widget is a quick and easy way to embed a search box on your custom 404 page and provide users with useful information designed to help them find the information they need. Where it can, the Google widget will also suggest other ways for the user to find the information they need, thus increasing the likelihood that they’ll continue to explore your site.\u003C\u002Fp>\n\u003Cp>For best results, you should set up a \u003Ca href=\"http:\u002F\u002Fwww.google.com\u002Fwebmasters\u002F\" title=\"Google\" rel=\"nofollow ugc\">Google webmaster account\u003C\u002Fa> and submit an XML sitemap of your blog to ensure the Google 404 widget works effectively.\u003C\u002Fp>\n\u003Cp>Find out more \u003Ca href=\"https:\u002F\u002Fsupport.google.com\u002Fwebmasters\u002Fanswer\u002F136085\" rel=\"nofollow ugc\">here…\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cp>Currently the plugin outputs the Google 404 widget in US English by default, or tries to use the current WordPress language.\u003Cbr \u002F>\nYou can use the \u003Ccode>google_404_language\u003C\u002Fcode> filter to specify a different language code.\u003C\u002Fp>\n\u003Cp>Also looking to add the possibility to \u003Ca href=\"https:\u002F\u002Fsupport.google.com\u002Fwebmasters\u002Fanswer\u002F100044\" rel=\"nofollow ugc\">change the appearance\u003C\u002Fa> of the widget.\u003C\u002Fp>\n\u003Ch4>Please note\u003C\u002Fh4>\n\u003Cp>The Google 404 widget plugin is NOT a WordPress widget.\u003Cbr \u002F>\nIt is simply the term Google use to describe their enhanced 404 page script.\u003C\u002Fp>\n\u003Ch4>Adoption Story\u003C\u002Fh4>\n\u003Cp>This plugin was originally developed by \u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fhusobj\u002F\" rel=\"nofollow ugc\">Ben Huson\u003C\u002Fa> and was adopted in September 2014 thanks to the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Ftags\u002Fadopt-me\" rel=\"ugc\">adopt-me\u003C\u002Fa> tag.\u003C\u002Fp>\n\u003Ch4>Coming Soon!\u003C\u002Fh4>\n\u003Cp>The ability to customize the CSS from an options page within the WordPress Admin area, attempt to dynamically inject the Google search box without needing to modify your template files, and more!\u003C\u002Fp>\n","Add Google search capabilities to your site's 404 \"page not found\" template.",50,13055,100,1,"2019-11-28T04:59:00.000Z","5.3.21","4.4","5.3",[73,74,75],"404","error","google","https:\u002F\u002Fwww.binarytemplar.com\u002Fgoogle-404","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fgoogle-404.2.1.zip",{"slug":79,"name":80,"version":81,"author":5,"author_profile":6,"description":82,"short_description":83,"active_installs":84,"downloaded":85,"rating":66,"num_ratings":67,"last_updated":86,"tested_up_to":87,"requires_at_least":88,"requires_php":71,"tags":89,"homepage":95,"download_link":96,"security_score":9,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"cf7-support-deprecated-settings","Contact Form 7: Support Deprecated Settings","0.4","\u003Cp>Contact Form 7 no longer supports the \u003Ccode>on_sent_ok\u003C\u002Fcode> and \u003Ccode>on_submit\u003C\u002Fcode> settings available on the Additional Settings screen as of version 5.0 of CF7. Both settings were deprecated before this release, which was why this plugin was first created. \u003Ca href=\"https:\u002F\u002Fcontactform7.com\u002Fadditional-settings\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fcontactform7.com\u002Fadditional-settings\u002F\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>This plugin is meant to be a band-aid to quickly get your Additional Settings working. It reads the Additional Settings data and adds a javascript block when the form is output on the page, using DOM Events as suggested by the CF7 author. \u003Ca href=\"https:\u002F\u002Fcontactform7.com\u002Fdom-events\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fcontactform7.com\u002Fdom-events\u002F\u003C\u002Fa>\u003C\u002Fp>\n","Provide continued support for on_sent_ok and on_submit within Contact Form 7's Additional Settings",10,1587,"2018-02-02T21:38:00.000Z","4.9.29","4.0",[90,91,92,93,94],"contact","contact-form","email","form","javascript","https:\u002F\u002Fgithub.com\u002Fdmchale\u002Fcf7-support-deprecated-settings","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcf7-support-deprecated-settings.0.4.zip",{"slug":98,"name":99,"version":100,"author":5,"author_profile":6,"description":101,"short_description":102,"active_installs":84,"downloaded":103,"rating":66,"num_ratings":67,"last_updated":104,"tested_up_to":105,"requires_at_least":106,"requires_php":50,"tags":107,"homepage":110,"download_link":111,"security_score":9,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"disablemu","DisableMU","1.1","\u003Cp>Redefines the location of the \u002Fmu-plugins directory, via writing constants to your wp-config.php file, to ensure that no code published to the default location will automatically run on your website.\u003C\u002Fp>\n\u003Cp>Since many site administrators are not using \u002Fmu-plugins, we want to be sure that no mu-plugins “suddenly” appear on our website due to their nature: auto-activation is BAD when you didn’t intend for code to be there!\u003C\u002Fp>\n\u003Cp>DisableMU is not for every website. Many development houses, system admins, and hosting companies have very legitimate uses for \u002Fmu-plugins and have built business plans around utilizing this feature of WordPress. By installing and activating DisableMU on your website, you may break things. Please exercise caution and only utilize this plugin if you know what you are doing. As with most plugins, DisableMU is written with the intent of being helpful but you are responsible for its use or actions on your own website.\u003C\u002Fp>\n","Redefines the location of the \u002Fmu-plugins directory to ensure that no code published to the default location will automatically run on your website.",2188,"2016-02-09T03:21:00.000Z","4.4.34","3.0.1",[29,108,109],"mu-plugins","security","http:\u002F\u002Fwww.binarytemplar.com\u002FdisableMU","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdisablemu.1.1.zip"]