[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f9NAAQwYrBfnJskufJ9KKgfOTZjVhaj4Rx0r_M_tJQo4":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},"philipnewcomer","Philip Newcomer","https:\u002F\u002Fprofiles.wordpress.org\u002Fphilipnewcomer\u002F",7,4490,85,30,84,"2026-04-05T02:26:29.787Z",[14,39,59,79,98,117,136],{"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},"responsive-image-maps","Responsive Image Maps","1.4","\u003Cp>This plugin simply packages the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fstowball\u002FjQuery-rwdImageMaps\" rel=\"nofollow ugc\">RWD Image Maps\u003C\u002Fa> jQuery plugin for use in WordPress, providing an easy way to make image maps responsive in a WordPress theme.\u003C\u002Fp>\n\u003Cp>This plugin is licensed under the GPLv2, and the jQuery plugin is licensed under the MIT license.\u003C\u002Fp>\n\u003Ch3>Javascript Warning\u003C\u002Fh3>\n\u003Cp>It goes without saying, but the RWD Image Maps jQuery plugin requires javascript to be enabled in the user’s browser for it to work its magic.\u003C\u002Fp>\n\u003Ch3>Need Help?\u003C\u002Fh3>\n\u003Cp>If you have questions or problems with the RWD Image Maps \u003Cstrong>jQuery\u003C\u002Fstrong> plugin itself (not the WordPress wrapper for it), go to the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fstowball\u002FjQuery-rwdImageMaps\" rel=\"nofollow ugc\">jQuery RWD Image Maps plugin page\u003C\u002Fa> on GitHub.\u003C\u002Fp>\n","Makes image maps responsive by packaging the RWD Image Maps jQuery plugin for use in WordPress.",4000,57177,98,64,"2017-11-28T17:28:00.000Z","4.1.42","3.0","",[29,30,31,32,33],"image","image-map","jquery","map","responsive","http:\u002F\u002Fphilipnewcomer.net\u002Fwordpress-plugins\u002Fresponsive-image-maps\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fresponsive-image-maps.1.4.zip",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":47,"num_ratings":48,"last_updated":49,"tested_up_to":50,"requires_at_least":51,"requires_php":27,"tags":52,"homepage":57,"download_link":58,"security_score":9,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"show-hidden-post-meta","Show Hidden Post Meta","1.0.1","\u003Cp>This plugin makes all custom fields (post meta) visible in the “Custom Fields” meta box on post edit screens.\u003C\u002Fp>\n","Makes hidden post meta visible on post edit screens",300,8139,86,6,"2019-09-25T22:40:00.000Z","5.2.24","3.2",[53,54,55,56],"admin","custom-fields","meta","post-meta","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fshow-hidden-post-meta\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fshow-hidden-post-meta.1.0.1.zip",{"slug":60,"name":61,"version":62,"author":5,"author_profile":6,"description":63,"short_description":64,"active_installs":65,"downloaded":66,"rating":65,"num_ratings":67,"last_updated":68,"tested_up_to":69,"requires_at_least":70,"requires_php":27,"tags":71,"homepage":77,"download_link":78,"security_score":9,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"author-post-ratings","Author Post Ratings","1.1.1","\u003Cp>There are plenty of plugins available which allow site \u003Cem>visitors\u003C\u002Fem> to rate posts, but I didn’t find any that gave the post \u003Cem>author\u003C\u002Fem> that functionality, so I wrote this plugin. \u003Cem>Author Post Ratings\u003C\u002Fem> adds a meta box to the post edit screen, allowing you to chose a 1-5 star rating for the post, or to leave it unrated. The plugin will automatically add the post rating (using stars, and an optional label) to the top or bottom of the post. If you wish, you can disable that functionality altogether and use a shortcode to insert the post rating anywhere in the post you choose. The plugin supports ratings for posts, pages, and custom post types, all of which can be individually enabled or disabled in the plugin settings. It is also fully internationalized, with Spanish language translation files included.\u003C\u002Fp>\n\u003Ch3>Translating the Plugin\u003C\u002Fh3>\n\u003Cp>The post rating label text can be changed in the plugin settings, so no translation is required for the frontend (public side) of the site. However, if you wish to translate the backend settings interface, the plugin is fully internationalized and ready for translation. There is a .po and a .mo file included in the plugin’s ‘languages’ directory for your convenience.\u003C\u002Fp>\n\u003Cp>The plugin includes the following translations:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Spanish\u003Cbr \u002F>\n\u003Cem>courtesy of \u003Ca href=\"http:\u002F\u002Fwww.webhostinghub.com\u002F\" rel=\"nofollow ugc\">WebHostingHub\u003C\u002Fa>\u003C\u002Fem>.\u003C\u002Fli>\n\u003C\u002Ful>\n","Allows a post author to assign a simple 1-5 star rating to a post, page, or custom post type, which will then be displayed on the post.",100,15256,8,"2013-12-12T14:53:00.000Z","3.7.41","3.1",[72,73,74,75,76],"author","custom-post-type","post","rating","stars","http:\u002F\u002Fphilipnewcomer.net\u002Fwordpress-plugins\u002Fauthor-post-ratings\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fauthor-post-ratings.1.1.1.zip",{"slug":80,"name":81,"version":82,"author":5,"author_profile":6,"description":83,"short_description":84,"active_installs":85,"downloaded":86,"rating":65,"num_ratings":87,"last_updated":88,"tested_up_to":89,"requires_at_least":26,"requires_php":27,"tags":90,"homepage":96,"download_link":97,"security_score":9,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"widget-output-filters","Widget Output Filters","1.2.0","\u003Cp>Sometimes developers need to filter the output of a widget that does not have its own output filter built-in. This plugin provides a filter which will allow developers to filter any widget’s output, regardless of whether it has that capability natively or not.\u003C\u002Fp>\n\u003Cp>This plugin was inspired by a similar filter in the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwidget-logic\u002F\" rel=\"ugc\">Widget Logic\u003C\u002Fa> plugin, and essentially duplicates that functionality, but with more flexibility.\u003C\u002Fp>\n\u003Cp>Usage instructions are \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fphilipnewcomer\u002Fwidget-output-filters\" rel=\"nofollow ugc\">on GitHub\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>This plugin is developed \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fphilipnewcomer\u002Fwidget-output-filters\" rel=\"nofollow ugc\">on GitHub\u003C\u002Fa>, and is available as a \u003Ca href=\"https:\u002F\u002Fpackagist.org\u002Fpackages\u002Fphilipnewcomer\u002Fwp-widget-output-filters\" rel=\"nofollow ugc\">Composer package\u003C\u002Fa>.\u003C\u002Fp>\n","A library which enables developers to filter the output of any WordPress widget.",60,3640,3,"2016-09-12T21:25:00.000Z","4.6.30",[91,92,93,94,95],"filter","filters","output","widget","widgets","https:\u002F\u002Fphilipnewcomer.net\u002Fwordpress-plugins\u002Fwidget-output-filters\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwidget-output-filters.1.2.0.zip",{"slug":99,"name":100,"version":101,"author":5,"author_profile":6,"description":102,"short_description":103,"active_installs":104,"downloaded":105,"rating":65,"num_ratings":106,"last_updated":107,"tested_up_to":108,"requires_at_least":70,"requires_php":27,"tags":109,"homepage":115,"download_link":116,"security_score":9,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"wp-stripe-email-receipts","WP Stripe Email Receipts","1.0","\u003Cp>\u003Cem>WP Stripe Email Receipts\u003C\u002Fem> is an add-on for the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-stripe\u002F\" rel=\"ugc\">WP Stripe\u003C\u002Fa> plugin, which sends an email receipt to the user after a successful Stripe transaction.\u003C\u002Fp>\n\u003Cp>It provides a settings page where you can customize the “from” name, “from” email address, message subject, and message body text of the email that is sent to the user.\u003C\u002Fp>\n","WP Stripe Email Receipts is an add-on for the WP Stripe plugin, which sends an email receipt to the user after a successful Stripe transaction.",20,2168,1,"2013-06-24T12:51:00.000Z","3.5.2",[110,111,112,113,114],"email","receipt","stripe","wp-stripe","wp_stripe","http:\u002F\u002Fphilipnewcomer.net\u002Fwordpress-plugins\u002Fwp-stripe-email-receipts\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-stripe-email-receipts.1.0.zip",{"slug":118,"name":119,"version":120,"author":5,"author_profile":6,"description":121,"short_description":122,"active_installs":123,"downloaded":124,"rating":36,"num_ratings":36,"last_updated":125,"tested_up_to":126,"requires_at_least":127,"requires_php":27,"tags":128,"homepage":134,"download_link":135,"security_score":9,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"customizer-framework","Customizer Framework","0.1","\u003Cp>A lightweight and easy-to-use framework for the WordPress Customizer. Provides a simple and intuitive API for registering Customizer settings, including advanced control types. Automatically sanitizes settings based on the control type. Eliminates the tedious task of registering a setting, control, and sanitization function for each individual Customizer setting.\u003C\u002Fp>\n\u003Cp>The framework may be used by both plugins and themes, although since at this time the settings are saved as theme mods, any plugin settings will be specific to the active theme. Support for option type settings is planned.\u003C\u002Fp>\n\u003Cp>\u003Cem>This plugin is currently in beta, and may be subject to major changes as it matures.\u003C\u002Fem>\u003C\u002Fp>\n\u003Ch4>Issues and Support\u003C\u002Fh4>\n\u003Cp>Contribute to the project \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fphilipnewcomer\u002FCustomizer-Framework\" rel=\"nofollow ugc\">on GitHub\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Why a Framework for the Customizer?\u003C\u002Fh4>\n\u003Cp>The recent WordPress Customizer API suffers from some of the same issues afflicting the old Settings API. The Settings API was overcomplicated, unintuitive, and confusing. The result was a crop of theme option frameworks that have sprung up to make it easier for developers to create theme options. The Customizer API is a bit better, but it’s still more complicated than necessary, and registering Customizer settings is still a convoluted mess of settings functions, controls functions, and sanitization functions. Now, the ease of use which the theme option frameworks have provided for the Settings API is available for the Customizer, in the Customizer Framework plugin.\u003C\u002Fp>\n\u003Cp>The Customizer Framework aims to be a lightweight wrapper around the convoluted Customizer API, which makes it fun to be a WordPress developer again. Developers can now focus their time on creating great themes that utilize the Customizer, not on writing 500 lines of code in order to create 10 Customizer settings. Okay, so I might be exaggerating a bit. But not by much. Do you really want to spend your time registering a Customizer setting, then registering a control for that setting, and then writing a sanitization function for that setting? And that’s only for one setting! And then there’s the advanced controls, such as image or color, that require you to instantiate their own control class, requiring even more convoluted and unintuitive code. And why should you even have to care about the differece between a setting and a control? Don’t you have better things to spend your time on, like creating great WordPress themes? I thought so.\u003C\u002Fp>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Cp>Activate the plugin, or \u003Ccode>include\u003C\u002Fcode> it in your theme.\u003C\u002Fp>\n\u003Cp>Before creating any settings, you need to create any new Customizer \u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FClass_Reference\u002FWP_Customize_Manager\u002Fadd_section\" rel=\"nofollow ugc\">sections\u003C\u002Fa> that you wish to use. Any custom sections need to exist before you can add settings to them.\u003C\u002Fp>\n\u003Cp>Finally, initialize a new \u003Ccode>CustomizerFramework\u003C\u002Fcode> class, and add your settings:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>function mytheme_register_settings( $settings ) {\n\n    $settings[] = array(\n        'id'      => 'example_setting',\n        'label'   => 'Example Setting Label',\n        'section' => 'example-section',\n        'type'    => 'text', \u002F\u002F Optional, defaults to 'text'\n        'default' => 'Example section default text', \u002F\u002F Optional\n    );\n\n}\nadd_filter( 'customizer_framework_settings', 'mytheme_register_settings' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Setting Types\u003C\u002Fh4>\n\u003Cp>Here are the currently available setting types:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>checkbox\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>color\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>dropdown-pages\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>image\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>radio\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>select\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>text\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>textarea\u003C\u002Fcode> (requires WordPress 4.0)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The \u003Ccode>radio\u003C\u002Fcode> and \u003Ccode>select\u003C\u002Fcode> types require an additional \u003Ccode>choices\u003C\u002Fcode> parameter, containing an array of the valid choices:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>'choices' => array(\n    'choice_1' => 'Choice 1',\n    'choice_2' => 'Choice 2',\n    'choice_3' => 'Choice 3',\n),\n'default' => 'choice_1',\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>In addition, on WordPress 4.0, you can specify any additional HTML5 input types, such as \u003Ccode>url\u003C\u002Fcode> or \u003Ccode>date\u003C\u002Fcode>. You can also include an \u003Ccode>atts\u003C\u002Fcode> parameter, containing an array of additional input attributes which should be applied to the input:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>'type' => 'url',\n'atts' => array(\n    'placeholder' => 'http:\u002F\u002F',\n    'class'       => 'a-custom-css-class',\n),\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Sanitization\u003C\u002Fh4>\n\u003Cp>All settings are sanitized automatically, based on the setting type. If you wish to specify your own sanitization function for a setting, add a \u003Ccode>sanitize_cb\u003C\u002Fcode> parameter, containing the function name to be called, which should return the sanitized value.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>'sanitize_cb' => 'my_custom_example_setting_sanitization_function',\n\u003C\u002Fcode>\u003C\u002Fpre>\n","A lightweight and easy-to-use framework for the WordPress Customizer.",10,2051,"2014-07-28T20:48:00.000Z","4.0.38","3.4",[129,130,131,132,133],"customizer","framework","option","theme-customizer","wrapper","http:\u002F\u002Fphilipnewcomer.net\u002Fwordpress-customizer-framework\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcustomizer-framework.0.1.zip",{"slug":137,"name":138,"version":139,"author":5,"author_profile":6,"description":140,"short_description":141,"active_installs":36,"downloaded":142,"rating":36,"num_ratings":36,"last_updated":143,"tested_up_to":144,"requires_at_least":26,"requires_php":145,"tags":146,"homepage":151,"download_link":152,"security_score":9,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":153},"cdn-image-proxy","CDN Image Proxy","1.0.0","\u003Cp>When developing locally, it’s common to use a database dump from a production site. With large sites, it’s also common that the production site’s image uploads cannot be easily copied to the local environment, because there are simply too many of them.\u003C\u002Fp>\n\u003Cp>While local environments like \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FPilothouse-App\u002Fpilothouse\" rel=\"nofollow ugc\">Pilothouse\u003C\u002Fa> allow you to easily proxy image uploads to your local environment from the production site, that doesn’t work so well if you add or change one of the registered thumbnail sizes in your local copy of the theme, since the new thumbnail size can’t be proxied from production as it doesn’t exist there. You’re also not able to regenerate the needed thumbnail sizes locally, because the original image file is not present locally.\u003C\u002Fp>\n\u003Cp>\u003Cem>CDN Image Proxy\u003C\u002Fem> solves this problem by using \u003Ca href=\"https:\u002F\u002Fjetpack.com\u002Fsupport\u002Fphoton\u002F\" rel=\"nofollow ugc\">Jetpack Image CDN\u003C\u002Fa> (formerly Photon) to proxy image uploads from your production site. Jetpack Image CDN will automatically generate and serve any required thumbnail size on-the-fly, but \u003Cem>CDN Image Proxy\u003C\u002Fem> will tell it to look for the original image on your production server, rather than on your local URL.\u003C\u002Fp>\n\u003Cp>The result is that you can add or change registered image sizes locally whenever you want, and Jetpack Image CDN will generate and provide a CDN URL for whatever thumbnail size is required, sourced from the original image file located on the production site.\u003C\u002Fp>\n","Use Jetpack Image CDN (formerly Photon) to proxy image uploads from another site.",1320,"2018-02-16T14:22:00.000Z","4.9.29","5.4",[147,29,148,149,150],"cdn","jetpack","photon","proxy","https:\u002F\u002Fgithub.com\u002Fphilipnewcomer\u002FCDN-Image-Proxy","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcdn-image-proxy.zip","2026-03-15T14:54:45.397Z"]