[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f7zV6MUrH-ik9nPMyLcsbw1Bbf6P31_qfGfYQ2g3aXkU":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},"samuelaguilera","Samuel Aguilera","https:\u002F\u002Fprofiles.wordpress.org\u002Fsamuelaguilera\u002F",14,98200,92,30,88,"2026-04-04T13:46:27.753Z",[14,39,58,80,99,116,134,150,170,189,206,223,239,257],{"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":7,"last_updated":23,"tested_up_to":24,"requires_at_least":25,"requires_php":26,"tags":27,"homepage":33,"download_link":34,"security_score":35,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"disable-xml-rpc-pingback","Disable XML-RPC Pingback","1.2.2","\u003Cp>Stops abuse of your site’s XML-RPC by simply removing some methods used by attackers. While you can use the rest of XML-RPC methods.\u003C\u002Fp>\n\u003Cp>This is more friendly than disabling totally XML-RPC, that it’s needed by some plugins and apps (I.e. Mobile apps or some Jetpack’s modules).\u003C\u002Fp>\n\u003Cul>\n\u003Cli>The original one.\u003C\u002Fli>\n\u003Cli>Simple and effective.\u003C\u002Fli>\n\u003Cli>No marketing buzz.\u003C\u002Fli>\n\u003Cli>Maintained and \u003Cstrong>updated when needed\u003C\u002Fstrong> since 2014.\u003C\u002Fli>\n\u003Cli>100% compliant with \u003Cstrong>WordPress coding standards\u003C\u002Fstrong> which makes it fail safe.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>60,000+ active installations\u003C\u002Fstrong> can’t be wrong.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If you’re happy with the plugin \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fdisable-xml-rpc-pingback\u002Freviews\u002F?filter=5\" rel=\"ugc\">please don’t forget to give it a good rating\u003C\u002Fa>, it will motivate me to keep sharing and improving this plugin (and others).\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cp>Removes the following methods from XML-RPC interface.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>pingback.ping\u003C\u002Fli>\n\u003Cli>pingback.extensions.getPingbacks\u003C\u002Fli>\n\u003Cli>X-Pingback from HTTP headers. This will hopefully stops some bots from trying to hit your xmlrpc.php file.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Requirements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>WordPress 3.8.1 or higher.\u003C\u002Fli>\n\u003C\u002Ful>\n","Stops abuse of your site's XML-RPC by simply removing some methods used by attackers. While you can use the rest of XML-RPC methods.",60000,420220,78,"2025-11-24T11:09:00.000Z","6.8.5","4.8","5.6",[28,29,30,31,32],"ddos","pingback","rpc","xml","xml-rpc","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdisable-xml-rpc-pingback.1.2.2.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":47,"num_ratings":48,"last_updated":49,"tested_up_to":50,"requires_at_least":25,"requires_php":26,"tags":51,"homepage":33,"download_link":57,"security_score":35,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"attachment-pages-redirect","Attachment Pages Redirect","1.1.2","\u003Cp>There are three possible scenarios where this plugin does something. In all cases, the attachment page must exists, \u003Cstrong>the plugin will not run for deleted attachments\u003C\u002Fstrong>:\u003C\u002Fp>\n\u003Cp>A) A visitor lands on an attachment page and the parent post is available (not in trash or deleted). A 301 redirect will be issued to redirect the visitor to the parent post.\u003C\u002Fp>\n\u003Cp>B) A visitor lands on an attachment page and the parent post was already deleted from trash. A 302 redirect is issued to home page (this can be changed to 301 if you want, see FAQ for more details).\u003C\u002Fp>\n\u003Cp>C) A visitor lands on an attachment page and the parent post is in trash, therefore not available for the visitor. It returns a 404 error code to prevent endless redirection loop in old WP releases and redirecting to trashed\u002Fnot available posts.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>There is no options page\u003C\u002Fstrong>, simply activate it and will do the job.\u003C\u002Fp>\n\u003Cp>If you’re happy with the plugin \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fattachment-pages-redirect\u002Freviews\u002F?filter=5\" rel=\"ugc\">please don’t forget to give it a good rating\u003C\u002Fa>, it will motivate me to keep sharing and improving this plugin (and others).\u003C\u002Fp>\n\u003Ch4>Requirements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>WordPress 4.8 or higher.\u003C\u002Fli>\n\u003C\u002Ful>\n","Redirect attachment pages or return a 404 error for them based on the parent post status.",20000,181455,98,47,"2026-01-16T11:00:00.000Z","6.9.4",[52,53,54,55,56],"301","302","attachment","images","redirect","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fattachment-pages-redirect.1.1.2.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":26,"tags":71,"homepage":77,"download_link":78,"security_score":79,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"easy-add-thumbnail","Easy Add Thumbnail","1.1.3","\u003Cp>\u003Cstrong>NOTE: This plugin functionality is guaranteed by more than 10,000 active installs. But before installing this plugin bear in mind that its only purpose is to ADD the feature image ID to your post (in the same way that you would do using WP editor), it does not remove ANYTHING after deactivation.\u003Cbr \u002F>\nBefore asking for support please read \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Feasy-add-thumbnail\u002Ffaq\u002F\" rel=\"ugc\">FAQ\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Ftopic\u002Fplease-read-before-posting-4\" rel=\"ugc\">this support thread\u003C\u002Fa>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch4>How it works?\u003C\u002Fh4>\n\u003Cp>Checks if the post (any post type with thumbnail support, including pages) has already a featured image associated, and if not sets it using one of the following methods:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\n\u003Cp>Dynamically, for old published posts, the featured images are set only when needed to show them in the frontend. This means that the featured image is set (only first time) when a visitor loads the page where it needs to be shown.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>For new content, the featured image is set in the publishing process.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>\u003Cstrong>No options page to setup\u003C\u002Fstrong>, simply install and activate.\u003C\u002Fp>\n\u003Cp>If you want to exclude certain post type (e.g. pages), you can do it by using a filter. See \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Feasy-add-thumbnail\u002Ffaq\u002F\" rel=\"ugc\">FAQ\u003C\u002Fa> for more details.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Easy Add Thumbnail doesn’t add any plugin data\u003C\u002Fstrong> to your WordPress database. It simply adds the _thumbnail_id meta key with the ID of the attachment to be used as feature image (just the same that WordPress does when you set it manually).\u003C\u002Fp>\n\u003Cp>Therefore it requires to have attached\u002Fuploaded at least one image to the post. If there’s not any image attached to the post, this plugin can’t help you.\u003C\u002Fp>\n\u003Cp>Easy Add Thumbnail has not any control over how\u002Fwhen\u002Fwhere your featured image is displayed in your site, \u003Cstrong>the display of the featured image in your site is TOTALLY controlled by your theme\u003C\u002Fstrong>, this includes size, position, display it or not…\u003C\u002Fp>\n\u003Ch4>Requirements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>WordPress 4.7 or higher.\u003C\u002Fli>\n\u003Cli>PHP 5.6 or higher.\u003C\u002Fli>\n\u003C\u002Ful>\n","Automatically sets the featured image to the first image uploaded into the post (any post type with thumbnail support). So easy like that...",8000,168019,90,52,"2023-10-05T16:22:00.000Z","6.3.8","4.7",[72,73,74,75,76],"automatic-feature-image","automatic-thumbail","featured-image","thumbnail","thumbnails","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Feasy-add-thumbnail\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Feasy-add-thumbnail.1.1.3.zip",85,{"slug":81,"name":82,"version":83,"author":5,"author_profile":6,"description":84,"short_description":85,"active_installs":86,"downloaded":87,"rating":88,"num_ratings":89,"last_updated":90,"tested_up_to":50,"requires_at_least":91,"requires_php":92,"tags":93,"homepage":33,"download_link":98,"security_score":35,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"fresh-forms-for-gravity","Fresh Forms for Gravity","1.5.6","\u003Cp>Caching is great for scenarios where your post or page content it’s not changed frequently, but if you have a form embedded to which you do changes very often or you’re using dynamic code, that doesn’t run for a cached page, or using third-party solutions relaying in dynamic live data (e.g. reCAPTCHA), using caching in these cases is going to cause issues. The same applies to certain automatic JS optimizations done by caching plugins that are known to break JS execution easily.\u003C\u002Fp>\n\u003Cp>An easy solution is to configure your caching plugin or proxy to exclude the page where the form is embedded, but you need also to remember this when you create a new page or embed a new form in an existing page…\u003C\u002Fp>\n\u003Cp>This plugin will take care of the above automatically doing the following:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Flush current cache on plugin activation. This is \u003Cstrong>required\u003C\u002Fstrong> in order to allow the next step to run.\u003C\u002Fli>\n\u003Cli>Dynamically check if there’s a Gravity Forms for any of the supported embedding methods (see below for the list).\u003C\u002Fli>\n\u003Cli>If so, it will prevent post\u002Fpage from being cached by any of the supported caching plugins, browsers and CDN\u002FProxies.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Embedding methods supported:\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>WordPress default editor, shortcode or Gutenberg block\u003C\u002Fstrong>. Content of any post type, including pages and custom posts.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>ACF\u003C\u002Fstrong> fields of type Text, Text Area, and WYSIWYG. \u003Cstrong>Disabled by default\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Avada\u003C\u002Fstrong>. The following elements has been proven to work: Content Boxes, “Gravity Form”, Modal, Text Block. Other elements could work too, but not tested.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Beaver Builder\u003C\u002Fstrong>. It will detect Gravity Forms shortcodes added to a Text Editor module.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Conversational Forms\u003C\u002Fstrong> add-on. It will automatically detect any form page using the \u003Cstrong>conversational_form\u003C\u002Fstrong> post type (requires Conversational Forms add-on 1.3.0+).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Divi\u003C\u002Fstrong>. It should work with any of the default modules where you can insert a GF shortcode into the content. e.g. Call To Action, Text, Tabs…\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Elementor\u003C\u002Fstrong>. The following widgets added to the post content are supported: Shortcode, Text.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fessential-addons-for-elementor-lite\u002F\" rel=\"ugc\">Essential Addons for Elementor\u003C\u002Fa> Gravity Forms widget.\u003C\u002Fli>\n\u003Cli>GravityKit Gravity Forms Widget for Elementor.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>PowerPack for Beaver Builder\u003C\u002Fstrong> Gravity Forms Styler module.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fultimate-addons-for-beaver-builder-lite\u002F\" rel=\"ugc\">Ultimate Addons for Beaver Builder\u003C\u002Fa> Gravity Forms Styler module.\u003C\u002Fli>\n\u003Cli>Ultimate Addons for Elementor By Brainstorm Force.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WooCommerce Gravity Forms Product Add-ons\u003C\u002Fstrong> by Lucas Stark.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WPBakery Page Builder\u003C\u002Fstrong>. The following elements has been proven to work: “Gravity Form”, Text Block. Other elements could work too, but not tested.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-tools-gravity-forms-divi-module\u002F\" rel=\"ugc\">WP Tools Gravity Forms Divi Module\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If you’re not using any of the above embedding methods you can still use Fresh Forms with a filter to pass the ID number of the posts where you want to run Fresh forms. You can also make Fresh Forms to add a cookie when a form is detected to use this cookie as a way to skip caching for hosts using Varnish based caching. Please see FAQ for more details.\u003C\u002Fp>\n\u003Cp>There’s no options page. Only the plugin version is saved to the database to be able to handle actions after an update when needed, \u003Cstrong>no other data is stored\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>It should work with any caching plugin with support for DONOTCACHEPAGE constant, and proxies respecting the use Cache-Control HTTP header.\u003C\u002Fp>\n\u003Cp>Caching and Optimization plugins \u003Cstrong>supported\u003C\u002Fstrong>:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Autoptimize\u003C\u002Fli>\n\u003Cli>Cache Enabler\u003C\u002Fli>\n\u003Cli>Comet Cache\u003C\u002Fli>\n\u003Cli>Hummingbird\u003C\u002Fli>\n\u003Cli>Kinsta Cache\u003C\u002Fli>\n\u003Cli>LiteSpeed Cache\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fpage-optimize\u002F\" rel=\"ugc\">Page Optimize\u003C\u002Fa> (Script concatenation only)\u003C\u002Fli>\n\u003Cli>Perfmatters (Delay JS exclusions only)\u003C\u002Fli>\n\u003Cli>Speed Optimizer (by SiteGround, the plugin with more name changes in the history of WordPress!)\u003C\u002Fli>\n\u003Cli>Surge\u003C\u002Fli>\n\u003Cli>W3 Total Cache\u003C\u002Fli>\n\u003Cli>WP Engine System\u003C\u002Fli>\n\u003Cli>WP Fastest Cache\u003C\u002Fli>\n\u003Cli>WP Optimize\u003C\u002Fli>\n\u003Cli>WP Rocket\u003C\u002Fli>\n\u003Cli>WP Super Cache\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Caching plugins \u003Cstrong>NOT supported\u003C\u002Fstrong>:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Breeze. It doesn’t support DONOTCACHEPAGE constant or filters to skip caching. \u003Cstrong>Check FAQ for a workaround.\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>NitroPack. It doesn’t support DONOTCACHEPAGE constant or filters to skip caching. \u003Cstrong>Check FAQ for a workaround.\u003C\u002Fstrong>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Cloudflare and other CDN\u002Fproxies:\u003C\u002Fp>\n\u003Cp>This plugin will add appropriate HTTP header to pages with a Gravity Forms form to exlude the page HTML from caching when the web host setup allows it.\u003C\u002Fp>\n\u003Cp>By default Cloudflare doesn’t cache the page HTML, it does only when you have configured it to “Cache Everything”. In this case, after activating the plugin, you need to purge cache in your Cloudflare account or wait for cache expiration to let Cloudflare know the page must be excluded from caching.\u003C\u002Fp>\n\u003Cp>Certain hosts like \u003Cstrong>WP Engine and Kinsta don’t allow HTTP headers modification from WordPress side of things\u003C\u002Fstrong>, therefore Cloudflare support will not work for these hosts.\u003C\u002Fp>\n\u003Cp>Other proxy services should work in a similar way, but I don’t have access to test any other proxy service. Feel to reach me if you want to provide me access to add support for your proxy service (documentation for the proxy would be required).\u003C\u002Fp>\n\u003Cp>Note for these cases (caching is done by an external service), Fresh Forms can just include the HTTP header when your web host allows it. Once the header is added, it’s up to the CDN\u002Fproxy being used to obey the header and skip caching for the page.\u003C\u002Fp>\n\u003Ch4>Requirements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>PHP 7.0 or higher.\u003C\u002Fli>\n\u003Cli>WordPress 4.9 or higher.\u003C\u002Fli>\n\u003Cli>Gravity Forms 2.3 or higher.\u003C\u002Fli>\n\u003Cli>Only forms embedded using classic editor shortcode or Gutenberg block are supported.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Usage\u003C\u002Fh4>\n\u003Cp>Just install and activate. No settings required except for ACF support (see FAQ).\u003C\u002Fp>\n","Prevent supported caching and JS optimization plugins breaking Gravity Forms.",3000,50365,94,7,"2026-01-08T17:06:00.000Z","4.9","7.0",[94,95,96,97],"cache","caching","gravity-forms","gravityforms","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffresh-forms-for-gravity.1.5.6.zip",{"slug":100,"name":101,"version":102,"author":5,"author_profile":6,"description":103,"short_description":104,"active_installs":86,"downloaded":105,"rating":9,"num_ratings":106,"last_updated":107,"tested_up_to":108,"requires_at_least":91,"requires_php":26,"tags":109,"homepage":33,"download_link":115,"security_score":35,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"sanitize-spanish-filenames","Clean Filenames","1.2.4","\u003Ch4>Features\u003C\u002Fh4>\n\u003Ch4>It takes the following steps for getting cleaner and safe to use filenames\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Removes or replace special\u002Finternational characters that can make your filenames not compliant with servers that don’t have support for international locales and filenames, or third-party services. (e.g. ‘España.png’ will become ‘Espana.png’, ‘prüfen’ will become ‘prufen’).\u003C\u002Fli>\n\u003Cli>Replaces any ‘+’ in the filename with ‘-‘ (e.g. ‘A+nice+picture.png’ will become ‘A-nice-picture.png’).\u003C\u002Fli>\n\u003Cli>Replaces any ‘.’ character before the one used for file extension with ‘-‘(e.g. ‘A.nice.picture.png’ will become ‘A-nice-picture.png’).\u003C\u002Fli>\n\u003Cli>After running all character replacement filters, a filter is applied to ensure that the filename only contains letters, numbers, underscores, dashes, and dots. Any other character will be removed from the filename.\u003C\u002Fli>\n\u003Cli>And finally all letters in the filename are set to lowercase to prevent issues with case insensitive systems. \u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This reduces problems with some servers, services, plugins… That may have problems handling filenames with special or international characters.\u003C\u002Fp>\n\u003Cp>The plugin does its job during file upload process, so it’ll change only filenames for files being \u003Cem>uploaded after plugin activation\u003C\u002Fem>.\u003C\u002Fp>\n\u003Cp>It supports a large number of international characters, including but not only, characters from belarusian, cyrillic alphabet, czech, german, hebrew, hungarian, russian, polish, spanish, ukrainian, and some other special characters (e.g. №, @, $, etc.).\u003C\u002Fp>\n\u003Cp>If you have any questions or need support, please check FAQ for additional information before asking.\u003C\u002Fp>\n\u003Ch4>Requirements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>WordPress 3.0 or higher\u003C\u002Fli>\n\u003C\u002Ful>\n","Removes or replace international or special characters that can make your filenames not compliant with some servers or services.",28857,8,"2025-04-14T15:06:00.000Z","6.7.5",[110,111,112,113,114],"filename","international-characters","sanitize","upload","utf-8","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsanitize-spanish-filenames.1.2.4.zip",{"slug":117,"name":118,"version":119,"author":5,"author_profile":6,"description":120,"short_description":121,"active_installs":122,"downloaded":123,"rating":9,"num_ratings":124,"last_updated":125,"tested_up_to":24,"requires_at_least":91,"requires_php":92,"tags":126,"homepage":132,"download_link":133,"security_score":35,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"sar-friendly-smtp","SAR Friendly SMTP","1.2.6","\u003Cp>There are A LOT of SMTP plugins for WordPress, some uses third-party libraries with no too much luck, others looks like the same plugin (almost identical source code) but with different name…\u003C\u002Fp>\n\u003Cp>Most of them overwrites from address and from name fields ALWAYS, breaking functionality of some other plugins that send emails using wp_mail() function.\u003C\u002Fp>\n\u003Cp>So the history repeats again, I can’t find one simple plugin that fits my needs, so I created one for myself and share it with you in the hope that you’ll find it useful.\u003C\u002Fp>\n\u003Cp>If you’re happy with the plugin \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fsar-friendly-smtp\u002Freviews\u002F?filter=5\" rel=\"ugc\">please don’t forget to give it a good rating\u003C\u002Fa>, it will motivate me to keep sharing and improving this plugin (and others).\u003C\u002Fp>\n\u003Cp>\u003Cstrong>IMPORTANT:\u003C\u002Fstrong> Support requests must be created using the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fsamuelaguilera\u002Fsar-friendly-smtp\u002Fissues\" rel=\"nofollow ugc\">Issues tab at the Github repository\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>KISS principle.\u003C\u002Fli>\n\u003Cli>No third-party libraries for SMTP, uses WordPress core.\u003C\u002Fli>\n\u003Cli>Respect fields modified by other plugins (e.g. Gravity Forms).\u003C\u002Fli>\n\u003Cli>Option to enable debug mode (logs communication between WordPress and your SMTP server in PHP’s error_log file, check \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fsar-friendly-smtp\u002Ffaq\u002F\" rel=\"ugc\">FAQ\u003C\u002Fa> for more details).\u003C\u002Fli>\n\u003Cli>Uses WordPress settings API for settings page, making it secure by default.\u003C\u002Fli>\n\u003Cli>Custom capability for settings access, so you can allow non administrator users to access to the settings page if you need it using \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fuser-role-editor\u002F\" rel=\"ugc\">User Role Editor\u003C\u002Fa> (or any other similar plugin).\u003C\u002Fli>\n\u003Cli>Send Email Test page. Allowing you to test if WordPress is able to send emails using the SMTP server details provided.\u003C\u002Fli>\n\u003Cli>Constants available to override settings using wp-config.php (useful to set same settings network-wide on a multi-site installation).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Requirements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>PHP 7.0 or higher.\u003C\u002Fli>\n\u003Cli>WordPress 4.9 or higher.\u003C\u002Fli>\n\u003Cli>SMTP server 🙂\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>It may work with older versions of PHP and WordPress (and it does in fact at the time of writing this), but I don’t support anything older than the versions mentioned above.\u003C\u002Fp>\n\u003Ch4>Usage\u003C\u002Fh4>\n\u003Cp>Just install in your WordPress like any other plugin, activate it and fill settings using your SMTP server details. If you’re not sure about what you need to put in each field, ask to your SMTP server support.\u003C\u002Fp>\n\u003Ch4>Developers\u003C\u002Fh4>\n\u003Cp>If you want to contribute to the development of this plugin fixing a bug or \u003Cstrong>suggesting\u003C\u002Fstrong> any improvement, feel free to submit a pull request to this repo.\u003C\u002Fp>\n","A friendly SMTP plugin for WordPress. No third-party, simply using WordPress native possibilities.",2000,35681,46,"2025-05-16T07:12:00.000Z",[127,128,129,130,131],"email","notifications","phpmailer","sendmail","smtp","http:\u002F\u002Fwww.samuelaguilera.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsar-friendly-smtp.1.2.6.zip",{"slug":135,"name":136,"version":137,"author":5,"author_profile":6,"description":138,"short_description":139,"active_installs":140,"downloaded":141,"rating":142,"num_ratings":143,"last_updated":144,"tested_up_to":50,"requires_at_least":91,"requires_php":92,"tags":145,"homepage":33,"download_link":149,"security_score":35,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"gf-no-duplicates","GF No Duplicates","1.2","\u003Cp>Gravity Forms already has some built-in duplicate submission prevention techniques, including the No Duplicates setting for a field in your form, preventing the same field value from being used multiple times for the same form. Using this setting is a rock solid approach to avoid duplicate submissions, but it requires having a field in your form that you can consider as a source of unique data per submission.\u003C\u002Fp>\n\u003Cp>This add-on helps using the same idea, without requiring having a field to enable the No Duplicates setting, by dynamically adding a hidden input with a random token to the form, and checks the \u003Ca href=\"https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FWeb\u002FHTTP\u002FMethods\u002FPOST\" rel=\"nofollow ugc\">POST request\u003C\u002Fa> received for this token value to prevent duplicate submissions.\u003C\u002Fp>\n\u003Cp>This will \u003Cstrong>stop identical POST requests\u003C\u002Fstrong> from being accepted for entry creation, like the ones that some browsers will send when the browser back or refresh buttons are clicked or when browser tabs are restored in mobile devices.\u003C\u002Fp>\n\u003Ch4>Limitations\u003C\u002Fh4>\n\u003Col>\n\u003Cli>If for any reason the visitor manually fills the form with the same information, and submits it again, \u003Cstrong>blocking this visitor’s behavior is not within the scope of this plugin functionality\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>To put in another way, the add-on is intended to \u003Cstrong>block automated resend of the same POST request data, it doesn’t block submissions voluntarily initiated by the visitor\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Col>\n\u003Cli>If your site is still receiving repeated POST requests \u003Cstrong>created before enabling the add-on\u003C\u002Fstrong>, therefore not containing the token field, you would still receive duplicates for these entries. There’s no way for the add-on to be able stop duplicates for requests \u003Cstrong>created before enabling the add-on\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>How it works:\u003C\u002Fh4>\n\u003Col>\n\u003Cli>\u003Cstrong>When the add-on is enabled\u003C\u002Fstrong> a hidden input with a random token as value is added to each form dynamically in the front-end.\u003C\u002Fli>\n\u003Cli>When a POST request is received and handled by Gravity Forms, GF No Duplicates checks if this POST request has the token and if its value was used already in an existing entry \u003Cstrong>for the form tied to the POST request\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003Cli>If the token parameter exists but is empty or there’s any form entry where the token value was used already, GF No Duplicates stops the submission.\u003C\u002Fli>\n\u003Cli>The form is replaced with an error message, which contains a link to the form page, suggesting the visitor to click the link to start a fresh new submission.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Requirements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>PHP 7.0 or higher.\u003C\u002Fli>\n\u003Cli>WordPress 4.9 or higher.\u003C\u002Fli>\n\u003Cli>Gravity Forms 2.5 or higher.\u003C\u002Fli>\n\u003Cli>The page where the form is embedded must be \u003Cstrong>excluded from cache\u003C\u002Fstrong> (if you use any caching plugin or server cache, see note below).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Usage\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Install and activate it as you do with any other plugin.\u003C\u002Fli>\n\u003Cli>Enjoy!\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Optionally, you can customize the duplicate submission message shown to users from the settings page or using a filter (see the FAQ).\u003C\u002Fp>\n\u003Ch4>Note about Caching\u003C\u002Fh4>\n\u003Cp>The add-on functionality relies on a \u003Cstrong>random\u003C\u002Fstrong> token generated \u003Cstrong>dynamically\u003C\u002Fstrong>, so for obvious reasons caching the page where your form is embedded would prevent the add-on from working as expected. This is not a limitation of the add-on but the expected if you’re serving a static version of your page, which is the only reason to cache a page, you shouldn’t never cache pages where you expect dynamic data.\u003C\u002Fp>\n\u003Cp>Most caching plugins provide you a way to exclude URLs from cache, this is for a reason, use it.\u003C\u002Fp>\n\u003Cp>There are some web hosting providers using cache at server level and not providing their customers with an interface to exclude URLs from cache (e.g. WP Engine, Kinsta, …), you can still ask your host support staff to add the exclusion for you.\u003C\u002Fp>\n\u003Cp>You can also use \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Ffresh-forms-for-gravity\u002F\" rel=\"ugc\">Fresh Forms\u003C\u002Fa> for automated cache exclusion if you use any of the embedding methods and caching plugins supported (see Fresh Forms description for more details).\u003C\u002Fp>\n","Prevents duplicate Gravity Forms submissions caused by the same POST request sent more than once.",700,6674,80,1,"2026-01-13T09:35:00.000Z",[146,147,148,96,97],"duplicated-entry","duplicated-submission","duplicates","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fgf-no-duplicates.1.2.zip",{"slug":151,"name":152,"version":153,"author":5,"author_profile":6,"description":154,"short_description":155,"active_installs":140,"downloaded":156,"rating":157,"num_ratings":158,"last_updated":159,"tested_up_to":160,"requires_at_least":161,"requires_php":33,"tags":162,"homepage":168,"download_link":169,"security_score":79,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"jetpack-lite","Jetpack Lite","3.0.3","\u003Cp>A lot of people, like me, miss the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fstats\u002F\" rel=\"ugc\">WordPress.com Stats\u003C\u002Fa> standalone plugin and only wants this part of Jetpack.\u003C\u002Fp>\n\u003Cp>This plugins completely \u003Cstrong>prevent all modules in Jetpack from being loaded except for Stats and WP.me Shortlinks modules, this means that all other modules are not loaded by Jetpack in any way, saving memory and resources\u003C\u002Fstrong> in your WordPress and leaving Jetpack only with the same features of \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fstats\u002F\" rel=\"ugc\">WordPress.com Stats\u003C\u002Fa> plugin that sadly was discontinued long time ago and replaced by Jetpack by WordPress.com\u003C\u002Fp>\n\u003Cp>Current version of the plugin it’s pretty simple, it just uses a few filters provided by Jetpack, so it’s totally fail safe. Also nothing is saved to the database, so deactivating the plugin is enough to revert it effects.\u003C\u002Fp>\n\u003Cp>GDPR Notice: The author of Jetpack Lite doesn’t collect ANY data. Also no data is saved in your site by Jetpack Lite.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Automatically prevents Jetpack from loading any modules except for Stats and WP.me Shortlinks, saving system resources and cleaning the interface for modules that you don’t want to use.\u003C\u002Fli>\n\u003Cli>Disables Jetpack’s Ads (aka “just in time messages”).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Requirements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Jetpack.\u003C\u002Fli>\n\u003Cli>WordPress version required by Jetpack.\u003C\u002Fli>\n\u003C\u002Ful>\n","Prevents Jetpack from loading any modules except for Stats and WP.me Shortlinks modules. Jetpack is required!",88280,50,15,"2018-06-19T14:13:00.000Z","4.9.29","3.6",[163,164,165,166,167],"jetpack","statistics","stats","views","wordpress-com","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fjetpack-lite\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fjetpack-lite.3.0.3.zip",{"slug":171,"name":172,"version":173,"author":5,"author_profile":6,"description":174,"short_description":175,"active_installs":176,"downloaded":177,"rating":35,"num_ratings":178,"last_updated":179,"tested_up_to":180,"requires_at_least":181,"requires_php":33,"tags":182,"homepage":132,"download_link":188,"security_score":79,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"safe-paste","Safe Paste","1.1.9","\u003Cp>WordPress do a great job by default filtering potentially dangerous code inside your content. So this plugin is NOT about security.\u003C\u002Fp>\n\u003Cp>But people can break your site design without compromising your security… That’s the purpose of this little plugin.\u003C\u002Fp>\n\u003Cp>Do you have users that creates content for you?. Do you own an online Magazine?\u003C\u002Fp>\n\u003Cp>If you answer yes to at least one of the above questions, I’m sure you have minor design troubles in your site because of your users using copy\u002Fpaste (ofcourse without using TinyMCE buttons to remove code) while not being aware of all the HTML tags they are pasting…\u003C\u002Fp>\n\u003Cp>This plugin simply removes a lot of HTML tags (and non breaking space HTML entitie) from post and page content before inserting it to database. Preventing users (including you) to paste undesired HTML tags to the content.\u003C\u002Fp>\n\u003Cp>It only does his work while you’re editing your post\u002Fpage (it can be in any status). So it’ll do the job on the new post\u002Fpages you create after the activation of the plugin and in old content that you edit after the plugin activation.\u003C\u002Fp>\n\u003Cp>These are the HTML tags that stays:\u003C\u002Fp>\n\u003Cp>\u003Cp>\u003Cbr \u002F>\n\u003Ca> (allowed attributes: href, title).\u003Cbr \u002F>\n\u003Cimg> (allowed attributes: src, alt, class).\u003Cbr \u002F>\n\u003Ch1>\u003Cbr \u002F>\n\u003Ch2>\u003Cbr \u002F>\n\u003Ch3>\u003Cbr \u002F>\n\u003Ch4>\u003Cbr \u002F>\n\u003Ch5>\u003Cbr \u002F>\n\u003Ch6>\u003Cbr \u002F>\n\u003Cblockquote>\u003Cbr \u002F>\n\u003Col>\u003Cbr \u002F>\n\u003Cul>\u003Cbr \u002F>\n\u003Cli>\u003Cbr \u002F>\n\u003Cem>\u003Cbr \u002F>\n\u003Cstrong>\u003Cbr \u002F>\n\u003Cdel>\u003Cbr \u002F>\n\u003Ccode>\u003Cbr \u002F>\n\u003Cins>\u003C\u002Fp>\n\u003Cp>Any other HTML tag (or attributes) and   (non breaking space) should be removed.\u003C\u002Fp>\n\u003Cp>Users with ‘unfiltered_html’ WP core capability (by default administrator and editor roles), will be excluded from the filter.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>NOTE: This program is distributed under \u003Ca href=\"http:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-2.0.html\" rel=\"nofollow ugc\">GPL2\u003C\u002Fa> licence in the hope that it will be useful, but WITHOUT ANY WARRANTY. I’m not responsible of ANY trouble or damage your site may have due to the use of this plugin. YOU and only YOU are responsible of your site and having backups and restoration plans. If you use this plugin you’re accepting this.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FKISS_principle\" rel=\"nofollow ugc\">KISS\u003C\u002Fa> philosofy 🙂\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Requirements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>WordPress 4.x or higher.\u003C\u002Fli>\n\u003C\u002Ful>\n","Removes a lot of HTML tags from post and page content before inserting it to database. Preventing users to paste undesired HTML tags to content.",200,5254,5,"2020-04-10T12:46:00.000Z","5.4.19","4.0",[183,184,185,186,187],"editor","html","post-content","strip-tags","tinymce","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsafe-paste.1.1.9.zip",{"slug":190,"name":191,"version":192,"author":5,"author_profile":6,"description":193,"short_description":194,"active_installs":176,"downloaded":195,"rating":35,"num_ratings":196,"last_updated":197,"tested_up_to":198,"requires_at_least":70,"requires_php":33,"tags":199,"homepage":33,"download_link":205,"security_score":79,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"sar-disable-rest-api","Disable REST API for Real","2.1.1","\u003Cp>The WordPress REST API is a great resource, but if you don’t want to use it probably you will want to close this door to your WordPress.\u003C\u002Fp>\n\u003Cp>Unlike other popular plugins that aims to disable the REST API but \u003Cstrong>only return an error, processed by the REST API\u003C\u002Fstrong>, when a request is received, by default, this plugin \u003Cstrong>removes all filters and actions related to WordPress REST API, and returns a 404 error for requests sent to the REST API URL endpoints, effectively blocking any use of the REST API\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>Optionally you can set the \u003Cstrong>REST API setting in Settings -> General page\u003C\u002Fstrong> to “Logged In Only” for a less drastical action, to keep REST API access enabled but require the user to be logged in to accept the requests.\u003C\u002Fp>\n\u003Cp>If you’re happy with the plugin \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fsar-disable-rest-api\u002Freviews\u002F?filter=5\" rel=\"ugc\">please don’t forget to give it a good rating\u003C\u002Fa>, it will motivate me to keep sharing and improving this plugin (and others).\u003C\u002Fp>\n\u003Cp>\u003Cstrong>SUPPORT:\u003C\u002Fstrong> If you have any support question, please \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fsamuelaguilera\u002Fsar-disable-rest-api\u002Fissues\" rel=\"nofollow ugc\">create an issue at the Github repository\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Requirements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>WordPress 4.7 or higher.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Disable WordPress core REST API \u003Cstrong>for real\u003C\u002Fstrong> by removing all filters and actions related to it and returning a 404 error for requests sent to REST API URL endpoints (e.g. https:\u002F\u002Fexample.com\u002Fwp-json\u002Fwhatever ).\u003C\u002Fli>\n\u003Cli>Option to require user to be logged in to use the REST API instead of completely disable it.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Usage\u003C\u002Fh4>\n\u003Cp>To disable the REST API completely simply install the plugin from the Plugins page and enable it.\u003C\u002Fp>\n\u003Cp>If you don’t want to disable the REST API but require user to be logged in instead, go to Settings -> General page and set the REST API to option to “Logged In Only”, and click Save Changes.\u003C\u002Fp>\n\u003Cp>You can change the option back to “Off” if you want to disable the REST API again.\u003C\u002Fp>\n\u003Cp>To return to WordPress default, simply deactivate the plugin.\u003C\u002Fp>\n","Really prevents the REST API from handling requests (default) or require user to be logged in.",5863,3,"2019-11-14T23:42:00.000Z","5.3.21",[200,201,202,203,204],"api","json","rest","rest-api","wp-json","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsar-disable-rest-api.2.1.1.zip",{"slug":207,"name":208,"version":209,"author":5,"author_profile":6,"description":210,"short_description":211,"active_installs":176,"downloaded":212,"rating":35,"num_ratings":89,"last_updated":213,"tested_up_to":108,"requires_at_least":214,"requires_php":33,"tags":215,"homepage":221,"download_link":222,"security_score":9,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"sar-one-click-security","SAR One Click Security","1.3","\u003Cp>There’s a lot of WordPress security plugins with many many options and pages to setup. And that is fine if you know what to do.\u003Cbr \u002F>\nBut most of the times, you don’t need so much or simply you’re not sure about what to set or not.\u003C\u002Fp>\n\u003Cp>This plugin adds some extra security to your WordPress with only one click. \u003Cstrong>No options page, just activate it!\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cp>Like many other security plugins SAR One Click Security adds well known .htaccess rules, but only the ones probed to be safe to use in almost any type of site (including WooCommerce stores), to protect your WordPress from common attacks. This allows you to have a safer WordPress without worries about what protection you should be using.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Turn off ServerSignature directive, that may leak information about your web server.\u003C\u002Fli>\n\u003Cli>Turn off directory listing, avoiding bad configured hostings to leak your files.\u003C\u002Fli>\n\u003Cli>Blocks public access (from web) to following files that may leak information about your WordPress install: .htaccess, license.txt, readme.html, wp-config.php, wp-config-sample.php, install.php\u003C\u002Fli>\n\u003Cli>Blocks access to wp-login.php to dummy bots trying to register in WordPress sites that have registration disabled.\u003C\u002Fli>\n\u003Cli>Blocks requests looking for timthumb.php, reducing server load caused by bots trying to find it. (*)\u003C\u002Fli>\n\u003Cli>Blocks TRACE and TRACK request methods, preventing XST attacks.\u003C\u002Fli>\n\u003Cli>Blocks direct posting to wp-comments-post.php (most spammers do this) and access with blank User Agent, reducing spam comments a lot and also server load.\u003C\u002Fli>\n\u003Cli>Blocks direct access to PHP files in wp-content directory (this includes subdirectories like plugins or themes). Protecting you from a huge number of 0day exploits.\u003C\u002Fli>\n\u003Cli>Blocks direct POST to wp-login.php and access with blank User Agent, preventing most brute-force attacks and reducing server load.\u003C\u002Fli>\n\u003Cli>Blocks access to .txt files under any plugin\u002Ftheme directory to prevent scans for installed plugins\u002Fthemes.\u003C\u002Fli>\n\u003Cli>Blocks any query string trying to get a copy of the wp-config.php file.\u003C\u002Fli>\n\u003Cli>Blocks gf_page=upload query string argument, this was deprecated in Gravity Forms on May 2015, if your copy of Gravity Forms still uses it, update now!\u003C\u002Fli>\n\u003Cli>Removes version information from page headers. This includes not only the page header (html or xhtml) but also feed headers (rss, rss2, atom, rdf) and opml comments. Only the version number is removed, not the entire generator information.  \u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>(*) If your theme uses TimThumb, you can disable that blocking rule, check FAQ before installing the plugin to see how.\u003C\u002Fp>\n\u003Ch4>Requirements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>WordPress 3.9.2 or higher. (Works with WordPress network\u002Fmultisite installation).\u003C\u002Fli>\n\u003Cli>Apache 2.4.x web server\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>It has been tested in many servers including large providers like HostGator, Godaddy and 1&1 with optimal results, and it will work fine in any decent hosting service (that allows you to set options from .htaccess files).\u003C\u002Fp>\n\u003Cp>Anyway, if you get any problem after activating the plugin, check FAQ for instructions on how to manually uninstall it.\u003C\u002Fp>\n\u003Cp>If you’re not sure of which server is your hosting company using or if they allow to use custom .htaccess rules, I would recommend you to contact with your host support \u003Cstrong>before\u003C\u002Fstrong> installing the plugin.\u003C\u002Fp>\n\u003Ch4>Usage\u003C\u002Fh4>\n\u003Cp>To apply above mentioned security rules simply install and activate the plugin, no options page, no user setup!\u003C\u002Fp>\n\u003Cp>If you need to remove the security rules for some reason, simply deactivate the plugin. If you want to add them again, activate the plugin again, that easy 😉\u003C\u002Fp>\n\u003Cp>And remember, \u003Cstrong>if your theme uses TimThumb, check FAQ before installing the plugin\u003C\u002Fstrong>.\u003C\u002Fp>\n","Adds some extra security to your WordPress with only one click.",13616,"2025-03-03T20:53:00.000Z","3.9.2",[216,217,218,219,220],"firewall","hardening","htaccess","protection","security","http:\u002F\u002Fwww.samuelaguilera.com\u002Farchivo\u002Fprotege-wordpress-facilmente.xhtml","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsar-one-click-security.1.3.zip",{"slug":224,"name":225,"version":226,"author":5,"author_profile":6,"description":227,"short_description":228,"active_installs":35,"downloaded":229,"rating":36,"num_ratings":36,"last_updated":230,"tested_up_to":231,"requires_at_least":91,"requires_php":33,"tags":232,"homepage":132,"download_link":238,"security_score":79,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"tedtalks-embedder","TEDTalks Embedder","2.1","\u003Cp>Helps you to embed TED Talks videos on your self hosted WordPress by simply pasting the URL or using a shortcode.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>This plugin is not affiliated in any way with TED Conferences, LLC\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>IMPORTANT: \u003Cstrong>You can’t use this plugin and Jetpack’s shortcodes module at the same time\u003C\u002Fstrong>. But you can use this plugin and Jetpack if you deactivate first the Jetpack’s shortcodes module.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Easy and simple usage.\u003C\u002Fli>\n\u003Cli>Uses same shortcode used for WordPress.com\u003C\u002Fli>\n\u003Cli>You can set default values (in Settings -> Media) width, height, and language of TED Talks.\u003C\u002Fli>\n\u003Cli>Supports multiple TED Talks in the same post.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Requirements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>WordPress 4.9 or higher.\u003C\u002Fli>\n\u003Cli>You can’t have Jetpack’s shortcodes module activated.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Usage\u003C\u002Fh4>\n\u003Cp>Currently there’s not support for the TED Gutenberg block, and I don’t have any plan to add it in a near future.\u003C\u002Fp>\n\u003Cp>You can embed TED videos by simply pasting the URL for the video in your content or using the \u003Ca href=\"https:\u002F\u002Fen.support.wordpress.com\u002Fwordpress-editor\u002Fblocks\u002Fshortcode-block\u002F\" rel=\"nofollow ugc\">shortcode block\u003C\u002Fa> to insert a shortcode.\u003C\u002Fp>\n\u003Cp>Examples:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>[ted id=”210″ lang=”es”]\u003C\u002Fli>\n\u003Cli>[ted id=”http:\u002F\u002Fwww.ted.com\u002Ftalks\u002Fview\u002Fid\u002F210″ lang=”es”]\u003C\u002Fli>\n\u003Cli>[ted id=210 lang=fr width=560]\u003C\u002Fli>\n\u003Cli>[ted id=”210″]\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If you want to set default width, height and language values for your TED Talks, go to Settings –> Media to set the values and omit values defined in the shortcode (last example).\u003C\u002Fp>\n\u003Cp>By the way, this plugin was specially made for TEDxZaragoza ‘The Future of Happiness’, an independently organized TED event that was held on November 5, 2011 in Zaragoza (Spain).\u003C\u002Fp>\n","Helps you to embed TED Talks videos on your self hosted WordPress by simply pasting the URL or using a shortcode.",9822,"2019-04-26T22:15:00.000Z","5.2.24",[233,234,235,236,237],"oembed","talks","ted","tedtalks","tedx","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ftedtalks-embedder.2.1.zip",{"slug":240,"name":241,"version":242,"author":5,"author_profile":6,"description":243,"short_description":244,"active_installs":245,"downloaded":246,"rating":35,"num_ratings":247,"last_updated":248,"tested_up_to":160,"requires_at_least":249,"requires_php":33,"tags":250,"homepage":132,"download_link":256,"security_score":79,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"cookieless-comments","Cookieless Comments","1.1","\u003Cp>Disables WordPress comment cookies. A tiny but useful plugin for people looking to simplify EU cookie law compliance requirements.\u003C\u002Fp>\n\u003Cp>Comment cookies are only used to avoid unregistered users to put their name and URL in the comment form everytime they comment in your WordPress and to allow them to see their comments while they are in moderation queue.\u003C\u002Fp>\n\u003Cp>So if you’re ok with losing the above functionality, this plugin will:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Prevent the cookie to be inserted in the comment author browser.\u003C\u002Fli>\n\u003Cli>Remove the checkbox for cookie consent in the WP core comments form.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>NOTE: This is not legal advice and can’t substitute it, it’s only a tiny plugin to help you when you know your site and your responsabilities. If you need legal advice regarding to EU cookie law and your site in your country ask to a lawyer.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>GDPR Notice: The author of this plugins doesn’t collect ANY DATA. Also the plugin doesn’t store any data in the site.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch4>Requirements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>WordPress 3.8.1 or higher.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Usage\u003C\u002Fh4>\n\u003Cp>Simply install and activate, no options.\u003C\u002Fp>\n","Disables WordPress comment cookies to simplify EU cookie law compliance requirements.",60,2958,2,"2018-06-27T15:24:00.000Z","3.8.1",[251,252,253,254,255],"comments","cookie-law","cookies","gdpr","ley-de-cookies","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcookieless-comments.1.1.zip",{"slug":258,"name":259,"version":260,"author":5,"author_profile":6,"description":261,"short_description":262,"active_installs":263,"downloaded":264,"rating":36,"num_ratings":36,"last_updated":265,"tested_up_to":266,"requires_at_least":267,"requires_php":33,"tags":268,"homepage":274,"download_link":275,"security_score":79,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"shorten2ping","Shorten2Ping","1.4.8","\u003Cp>\u003Cstrong>IMPORTANT!!: At present Seesmic has blocked the API key for this plugin, you can \u003Ca href=\"http:\u002F\u002Fur1.es\u002FdjjSqf\" rel=\"nofollow ugc\">read more here\u003C\u002Fa>. So I have added support for using email notification, this is working for some users and not for others. Sorry but I can’t do more about this, so blame to Seesmic not me.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>UPDATE (2011\u002F08\u002F27): Ping.fm support will be removed in a future version of this plugin.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Sends \u003Cstrong>status\u003C\u002Fstrong> updates to \u003Ca href=\"http:\u002F\u002Fping.fm\" rel=\"nofollow ugc\">Ping.fm\u003C\u002Fa> (this means you can update Twitter, Facebook, LinkedIn, Plurk, and many others at once) everytime you publish a post. Using many shorteners or even your own domain for shortened permalinks. So this way you can send status to many sites at once if you have a Ping.fm account or send only to Twitter if you prefer that.\u003C\u002Fp>\n\u003Cp>If you find it useful, please consider to make a \u003Ca href=\"https:\u002F\u002Fwww.paypal.com\u002Fcgi-bin\u002Fwebscr?cmd=_s-xclick&hosted_button_id=8801680\" rel=\"nofollow ugc\">donation\u003C\u002Fa> to Shorten2Ping’s author (any amount will be appreciated).\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Send new posts notifications to \u003Cstrong>Ping.fm\u003C\u002Fstrong> service (account required).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Avoids to ping again when editing\u003C\u002Fstrong> previously pinged post or even when editing an old post not pinged before.\u003C\u002Fli>\n\u003Cli>Option to choose between \u003Cstrong>bit.ly, tr.im, YOURLS, su.pr, is.gd, j.mp, wp.me, cli.gs or even you own domain\u003C\u002Fstrong> for shortened permalinks.\u003C\u002Fli>\n\u003Cli>Option to turn off notification or shortener service. Now \u003Cstrong>you can use Shorten2Ping only for notification\u003C\u002Fstrong> if your domain is already short enough for you, \u003Cstrong>or use only to get shortened urls for your posts.\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Stores created shortened permalink\u003C\u002Fstrong> in a post meta field (used for template integration).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Using \u003Ccode>rel=\"shortlink\"\u003C\u002Fcode>\u003C\u002Fstrong> like in wp.me http:\u002F\u002Fwp.me\u002Fsf2B5-shorten, creating auto-discovery link tag for the short link on single post page header.\u003C\u002Fli>\n\u003Cli>You can use a \u003Cstrong>template tag for showing visitors the short URL\u003C\u002Fstrong> (using the same rel attribute as above for the shortened permalink).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Locale support\u003C\u002Fstrong>. Now available in English, Spanish, Italian and Traditional Chinese (zh_TW). See translation section for more info.\u003C\u002Fli>\n\u003Cli>WPMU compatible (you can have different settings for each blog).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Simple\u003C\u002Fstrong>, fast, and useful 🙂\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Requirements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>PHP 5.x with CURL and JSON enabled (maybe works too in PHP4, but not tested and not supported by me).\u003C\u002Fli>\n\u003Cli>Your hosting provider must allow the use of PHP mail() function if you choose ‘Ping.fm email’ notification method.\u003C\u002Fli>\n\u003Cli>WordPress 2.7.x or higher (maybe would work on older WP, but not tested and not supported by me).\u003C\u002Fli>\n\u003Cli>Required your own account for the third party services that you want to use.\u003C\u002Fli>\n\u003Cli>Not tested and not supported on IIS servers.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Translations\u003C\u002Fh4>\n\u003Cp>If you want to make a translation for your language, use the shorten2ping.pot included and (if you want) send me the files to correo@samuelaguilera.com for including it into the plugin package, you’ll be credited, of course (NOTE: No sponsored translations allowed).\u003C\u002Fp>\n\u003Cp>Credits for present translations:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Italian translation (it_IT) made by Riccardo Vianello AKA etms51\u003C\u002Fli>\n\u003Cli>Traditional Chinese translation (zh_TW) made by Pseric.\u003C\u002Fli>\n\u003Cli>French translation (fr_FR) made by Olivier.\u003C\u002Fli>\n\u003Cli>Polish translation (pl_PL) made by Darek Skonieczka. \u003C\u002Fli>\n\u003Cli>Spanish translation (es_ES) made by myself 🙂\u003C\u002Fli>\n\u003C\u002Ful>\n","Sends status updates to Ping.fm everytime you publish a post, using your own domain, bit.ly, wp.me, su.pr, is.gd and others for shortened permalinks.",40,41715,"2012-03-17T15:23:00.000Z","3.3.2","2.7",[269,270,271,272,273],"bit-ly","facebook","ping","ping-fm","twitter","http:\u002F\u002Fwww.samuelaguilera.com\u002Farchivo\u002Fshorten2ping-notifies-pingfm-bitly.xhtml","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fshorten2ping.1.4.8.zip"]