[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f87nRrBEJbaJQqEewy9zV4Zv75RwUzFhtEf-YdohAZj0":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},"acato","Acato","https:\u002F\u002Fprofiles.wordpress.org\u002Facato\u002F",5,11950,97,107,77,"2026-05-19T22:53:05.776Z",[14,41,62,83,101],{"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":36,"vuln_count":37,"unpatched_count":38,"last_vuln_date":39,"fetched_at":40},"wp-rest-cache","WP REST Cache","2026.1.3","\u003Cp>Are you facing speed issues, using the WordPress REST API? This plugin will allow WordPress to cache the responses of the REST API, making it much faster.\u003C\u002Fp>\n\u003Cp>This plugin offers:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Caching of all default WordPress REST API \u003Ccode>GET\u003C\u002Fcode>-endpoints.\u003C\u002Fli>\n\u003Cli>Caching of (custom) post type endpoints.\u003C\u002Fli>\n\u003Cli>Caching of (custom) taxonomy endpoints.\u003C\u002Fli>\n\u003Cli>Automated flushing of caches if (some of) its contents are edited.\u003C\u002Fli>\n\u003Cli>Manual flushing of all caches.\u003C\u002Fli>\n\u003Cli>Manual flushing of specific caches.\u003C\u002Fli>\n\u003Cli>A counter how many times a cache has been retrieved.\u003C\u002Fli>\n\u003Cli>Specifying after what time the cache should be timed out.\u003C\u002Fli>\n\u003Cli>Registering custom endpoints for caching.\u003C\u002Fli>\n\u003Cli>Automatic cache regeneration.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>WP REST Cache Pro\u003C\u002Fstrong>\u003Cbr \u002F>\nFor more advanced features, check out our \u003Ca href=\"https:\u002F\u002Fplugins.acato.nl\u002F\" rel=\"nofollow ugc\">WP REST Cache Pro\u003C\u002Fa> plugin:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Configure custom endpoints for caching through the wp-admin interface.\u003C\u002Fli>\n\u003Cli>Configure relationships within endpoints.\u003C\u002Fli>\n\u003Cli>No coding required.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Installation from within WordPress\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Visit ‘Plugins > Add New’ (or ‘My Sites > Network Admin > Plugins > Add New’ if you are on a multisite installation).\u003C\u002Fli>\n\u003Cli>Search for ‘WP REST Cache’.\u003C\u002Fli>\n\u003Cli>Activate the WP REST Cache plugin through the ‘Plugins’ menu in WordPress.\u003C\u002Fli>\n\u003Cli>Go to “after activation” below.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Installation manually\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Upload the \u003Ccode>wp-rest-cache\u003C\u002Fcode> folder to the \u003Ccode>\u002Fwp-content\u002Fplugins\u002F\u003C\u002Fcode> directory.\u003C\u002Fli>\n\u003Cli>Activate the WP REST Cache plugin through the ‘Plugins’ menu in WordPress.\u003C\u002Fli>\n\u003Cli>Go to “after activation” below.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>After activation\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Visit ‘Plugins > Must-Use’ (or ‘My Sites > Network Admin > Plugins > Must-Use’ if you are on a multisite installation).\u003C\u002Fli>\n\u003Cli>Check if the ‘WP REST Cache – Must-Use Plugin’ is there, if not copy the file \u003Ccode>wp-rest-cache.php\u003C\u002Fcode> from the \u003Ccode>\u002Fsources\u003C\u002Fcode> folder of the WP REST Cache Plugin to the folder \u003Ccode>\u002Fwp-content\u002Fmu-plugins\u002F\u003C\u002Fcode>.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>\u003Cstrong>Optionally:\u003C\u002Fstrong>\u003Cbr \u002F>\nThe default timeout for caches generated by the WP REST Cache plugin is set to 1 year. If you want to change this:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Visit ‘Settings > WP REST Cache’.\u003C\u002Fli>\n\u003Cli>Change the Cache timeout.\u003C\u002Fli>\n\u003C\u002Fol>\n","Enable caching of the WordPress REST API and auto-flush caches upon wp-admin editing.",10000,372181,98,42,"2026-03-03T09:38:00.000Z","6.8.5","4.7","7.0",[29,30,31,32,33],"api","cache","rest","rest-cache","wp-rest-api","https:\u002F\u002Fwww.acato.nl","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-rest-cache.2026.1.3.zip",94,2,0,"2026-03-23 00:00:00","2026-04-16T10:56:18.058Z",{"slug":42,"name":43,"version":44,"author":5,"author_profile":6,"description":45,"short_description":46,"active_installs":47,"downloaded":48,"rating":49,"num_ratings":50,"last_updated":51,"tested_up_to":52,"requires_at_least":26,"requires_php":53,"tags":54,"homepage":58,"download_link":59,"security_score":60,"vuln_count":38,"unpatched_count":38,"last_vuln_date":61,"fetched_at":40},"wp-rest-yoast-meta","WP REST Yoast Meta","2025.1.0","\u003Cp>\u003Cem>This plugin is no longer updated, but is open for adoption\u003C\u002Fem>\u003Cbr \u002F>\nAs of Yoast SEO version 16.7 the functionality provided by this plugin is now \u003Ca href=\"https:\u002F\u002Fdeveloper.yoast.com\u002Fcustomization\u002Fapis\u002Frest-api\u002F\" rel=\"nofollow ugc\">part of the Yoast SEO plugin\u003C\u002Fa> itself. This plugin will no longer be updated, but is open for adoption. If you are interested in adopting this plugin, please contact the authors.\u003C\u002Fp>\n\u003Cp>Are you using WordPress for a headless set-up, using the WP REST API? And would you like to use the Yoast SEO plugin just like you would for any other project? This plugin adds the meta tags generated by the Yoast SEO plugin to the WP REST API output, allowing your headless set-up to implement them. Also when you are using Yoast SEO Premium you have the option to retrieve redirects throught the API: this plugin adds a custom endpoint (\u003Ccode>\u002Fwp-rest-yoast-meta\u002Fv1\u002Fredirects\u003C\u002Fcode>) to provide those redirects in a JSON format. Since Yoast 11.0 JSON LD Schema.org data is also supported and is now also available through the WP REST API when using this plugin.\u003C\u002Fp>\n\u003Ch3>Installation from within WordPress\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Visit ‘Plugins > Add New’ (or ‘My Sites > Network Admin > Plugins > Add New’ if you are on a multisite installation).\u003C\u002Fli>\n\u003Cli>Search for ‘WP REST Yoast Meta’.\u003C\u002Fli>\n\u003Cli>Activate the WP REST Yoast Meta plugin through the ‘Plugins’ menu in WordPress.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Installation manually\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Upload the \u003Ccode>wp-rest-yoast-meta\u003C\u002Fcode> folder to the \u003Ccode>\u002Fwp-content\u002Fplugins\u002F\u003C\u002Fcode> directory.\u003C\u002Fli>\n\u003Cli>Activate the WP REST Yoast Meta plugin through the ‘Plugins’ menu in WordPress.\u003C\u002Fli>\n\u003C\u002Fol>\n","Adds meta tags as generated by Yoast SEO to the WP REST API. And adds a custom endpoint to retrieve all redirects as they are set in Yoast SEO Premium …",1000,32207,100,6,"2025-01-23T09:31:00.000Z","5.7.15","5.4",[55,29,56,33,57],"adopt-me","wp-rest","yoast","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-rest-yoast-meta.2025.1.0.zip",92,null,{"slug":63,"name":64,"version":65,"author":5,"author_profile":6,"description":66,"short_description":67,"active_installs":68,"downloaded":69,"rating":49,"num_ratings":70,"last_updated":71,"tested_up_to":72,"requires_at_least":26,"requires_php":73,"tags":74,"homepage":79,"download_link":80,"security_score":49,"vuln_count":81,"unpatched_count":38,"last_vuln_date":82,"fetched_at":40},"branded-social-images","Branded Social Images – Open Graph Images with logo and extra text layer","1.1.5","\u003Cp>Branded social images (open graph images) in just a few clicks.\u003C\u002Fp>\n\u003Cp>This plugin creates branded social images to match with your company’s style. Including a company logo and title.\u003Cbr \u002F>\nThese open graph images can either be auto-generated for the entire site or you have the option to overrule this per page\u002Fpost.\u003C\u002Fp>\n\u003Cp>Works with every (public) post-type in WordPress!\u003C\u002Fp>\n\u003Cp>Also tested with WOOCommerce.\u003C\u002Fp>\n\u003Cp>The version 2.0.0 branch even supports taxonomies, so you can brand your category and tag pages as well! Check it out on \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Facato-plugins\u002Fbranded-social-images\" title=\"Branded Social Images on GitHub\" rel=\"nofollow ugc\">GitHub\u003C\u002Fa>\u003C\u002Fp>\n","The simplest way to brand your social images. Provide all your social images (Open Graph images) with your brand en text. In just a few clicks.",900,15324,3,"2026-04-03T07:56:00.000Z","6.9.4","7.4",[75,76,77,78],"og-image","open-graph","open-graph-image","social-image","https:\u002F\u002Fgithub.com\u002Facato-plugins\u002Fbranded-social-images","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fbranded-social-images.1.1.5.zip",1,"2023-03-20 00:00:00",{"slug":84,"name":85,"version":86,"author":5,"author_profile":6,"description":87,"short_description":88,"active_installs":89,"downloaded":90,"rating":38,"num_ratings":38,"last_updated":91,"tested_up_to":72,"requires_at_least":92,"requires_php":73,"tags":93,"homepage":99,"download_link":100,"security_score":49,"vuln_count":38,"unpatched_count":38,"last_vuln_date":61,"fetched_at":40},"email-essentials","Email Essentials","6.0.3","\u003Cp>Email Essentials vastly reduces the chances of your emails being marked as spam or being rejected. Originally a debugging tool, it has grown into a full-fledged email enhancement plugin.\u003C\u002Fp>\n\u003Cp>Please note that this plugin is not a “we support any type of transport” Email plugin. For other protocols than SMTP, but rather to enhance the email sending capabilities of WordPress.\u003Cbr \u002F>\nIf you need to send emails with other protocols than SMTP, this plugin is not for you. You might want to look at plugins like Post SMTP (not affiliated).\u003C\u002Fp>\n\u003Cp>And since version 6.0.0, after more than 10 years of development, this plugin is now a FOSS plugin, meaning it is free to use, modify and distribute under the GPLv2 license.\u003C\u002Fp>\n\u003Cp>In return, we ask you to support the development of this plugin by contributing to the codebase, reporting bugs, and helping others in the community.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Responsible disclosure:\u003C\u002Fstrong>\u003Cbr \u002F>\nIf you find a vulnerability, please email us at \u003Ca href=\"mailto:responsibledisclosure@acato.nl\" rel=\"nofollow ugc\">responsibledisclosure@acato.nl\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Set a good From name and email address, automatically correcting it if needed. For example, a contact form is sent from the visitors email address, resulting in an invalid Sender address. This plugin will correct it to a valid email address. This plugin automatically corrects it.\u003C\u002Fli>\n\u003Cli>Correct envelope-from address; often forgotten, but important for deliverability.\u003C\u002Fli>\n\u003Cli>Reformat as HTML with plain text alternative; will detect the use of HTML ensures that emails are sent as HTML with a plain text alternative.\u003C\u002Fli>\n\u003Cli>Process shortcodes in your email content.\u003C\u002Fli>\n\u003Cli>UTF8 recoding, to ensure that special characters are correctly encoded in the email.\u003C\u002Fli>\n\u003Cli>Email Essentials allows for adding CSS, header, footer, and body template using filters, see below.\u003C\u002Fli>\n\u003Cli>Convert CSS to inline styles for better support in email clients\u003C\u002Fli>\n\u003Cli>SMTP configuration\u003C\u002Fli>\n\u003Cli>Send emails to multiple addressees as separate emails\u003C\u002Fli>\n\u003Cli>S\u002FMIME signing, using a supplied certificate, to ensure the authenticity of the email.\u003C\u002Fli>\n\u003Cli>DKIM signing, and providing all information needed to set up DKIM signing for your domain.\u003C\u002Fli>\n\u003Cli>Allow redirecting emails sent to the administrator to other email addresses based on the email subject.\u003C\u002Fli>\n\u003Cli>Allow redirecting emails sent to the moderators (e.g., for comments).\u003C\u002Fli>\n\u003Cli>Keep a history of outgoing emails (debugging, cleared on deactivation)\u003C\u002Fli>\n\u003Cli>Email receipt tracking (for investigative purposes only, see GDPR note)\u003C\u002Fli>\n\u003Cli>Re-send button for failed emails\u003C\u002Fli>\n\u003Cli>Allow sending emails delayed, to prevent sending too many emails at once. (Beta feature)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Important Note\u003C\u002Fh3>\n\u003Cp>This tool is for users who understand email delivery. If unsure, ask for help.\u003C\u002Fp>\n\u003Cp>\u003Cem>Under GDPR, storing and tracking emails is prohibited. The history feature is for investigative purposes only!\u003C\u002Fem>\u003C\u002Fp>\n\u003Ch3>External services\u003C\u002Fh3>\n\u003Cp>Email Essentials uses one external service by default, two if you create and define your own IP services.\u003C\u002Fp>\n\u003Col>\n\u003Cli>CloudFlare DNS over HTTPS (DoH). This is used to resolve domain names to IP addresses when (for example) checking SPF or DKIM records. In theory, it is possible to use PHPs own \u003Ccode>dns_get_record\u003C\u002Fcode> function, but in practice this often fails due to server DNS-resolve misconfiguration. Using CloudFlare’s DoH service ensures reliable DNS resolution. We only send the hostname (the domain part) to CloudFlare, no other data. Explicitly, we do NOT send any other information.\u003C\u002Fli>\n\u003Cli>The plugin can use an IP-address relay service to accurately determine the sender’s IP address. This is required to accurately check that the sender’s IP address is authorized to send email for the domain (SPF check). To use this, you will need to set up your own service, see documentation on filter \u003Ccode>acato_email_essentials_ip_services\u003C\u002Fcode>. Without this service, IP detection can be inaccurate because it will use the website itself as a relay. Use of a reverse proxy, load balancer etc. can lead to incorrect IP detection.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>WordPress Filters\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ccode>acato_email_essentials_settings\u003C\u002Fcode> — Filter plugin settings.\u003C\u002Fli>\n\u003Cli>\u003Ccode>acato_email_essentials_defaults\u003C\u002Fcode> — Filter default settings.\u003C\u002Fli>\n\u003Cli>\u003Ccode>acato_email_essentials_subject\u003C\u002Fcode> — Filter email subject.\u003C\u002Fli>\n\u003Cli>\u003Ccode>acato_email_essentials_body\u003C\u002Fcode> — Filter HTML body of the email.\u003C\u002Fli>\n\u003Cli>\u003Ccode>acato_email_essentials_head\u003C\u002Fcode> — Filter HEAD section of HTML email.\u003C\u002Fli>\n\u003Cli>\u003Ccode>acato_email_essentials_css\u003C\u002Fcode> — Filter CSS for the email.\u003C\u002Fli>\n\u003Cli>\u003Ccode>acato_email_essentials_minify_css\u003C\u002Fcode> — Filter CSS minification.\u003C\u002Fli>\n\u003Cli>\u003Ccode>acato_email_essentials_mail_is_throttled\u003C\u002Fcode> — Check if mail should be throttled.\u003C\u002Fli>\n\u003Cli>\u003Ccode>acato_email_essentials_mail_throttle_time_window\u003C\u002Fcode> — Set mail throttle time window.\u003C\u002Fli>\n\u003Cli>\u003Ccode>acato_email_essentials_mail_throttle_max_count_per_time_window\u003C\u002Fcode> — Set max emails per time window.\u003C\u002Fli>\n\u003Cli>\u003Ccode>acato_email_essentials_mail_throttle_batch_size\u003C\u002Fcode> — Set mail batch size.\u003C\u002Fli>\n\u003Cli>\u003Ccode>acato_email_essentials_ip_services\u003C\u002Fcode> — Define custom IP services for accurately determining the sender’s IP address.\u003C\u002Fli>\n\u003Cli>\u003Ccode>acato_email_essentials_ip_service\u003C\u002Fcode> — Filter individual IP service URLs.\u003C\u002Fli>\n\u003Cli>\u003Ccode>acato_email_essentials_website_root_path\u003C\u002Fcode> — Filter to supply the correct website root path in case of non-standard setups.\u003C\u002Fli>\n\u003Cli>\u003Ccode>acato_email_essentials_development_tlds\u003C\u002Fcode> — Filter development\u002Flocal TLDs.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>WordPress Filters in detail\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Plugin Settings\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>acato_email_essentials_settings\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Parameters:\u003Cbr \u002F>\n– (array) \u003Ccode>$settings\u003C\u002Fcode> The current settings of the plugin.\u003C\u002Fp>\n\u003Cp>Expected return:\u003Cbr \u002F>\n– (array) The new settings of the plugin.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>acato_email_essentials_defaults\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Parameters:\u003Cbr \u002F>\n– (array) \u003Ccode>$defaults\u003C\u002Fcode> The current default settings of the plugin.\u003C\u002Fp>\n\u003Cp>Expected return:\u003Cbr \u002F>\n– (array) The new default settings of the plugin.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Email Content\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>acato_email_essentials_subject\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Parameters:\u003Cbr \u002F>\n– (string) \u003Ccode>$the_subject\u003C\u002Fcode> Subject for the email.\u003Cbr \u002F>\n– (PHPMailer) \u003Ccode>$mailer\u003C\u002Fcode> The PHPMailer object (by reference).\u003C\u002Fp>\n\u003Cp>Expected return:\u003Cbr \u002F>\n– (string) The (altered) Subject.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>acato_email_essentials_body\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Parameters:\u003Cbr \u002F>\n– (string) \u003Ccode>$should_be_html\u003C\u002Fcode> A text that should be html, but might not yet be, your job to make a nice HTML body.\u003Cbr \u002F>\n– (PHPMailer) \u003Ccode>$mailer\u003C\u002Fcode> The PHPMailer object (by reference).\u003C\u002Fp>\n\u003Cp>Expected return:\u003Cbr \u002F>\n– (string) A text that should be html.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>acato_email_essentials_head\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Parameters:\u003Cbr \u002F>\n– (string) \u003Ccode>$the_head_section\u003C\u002Fcode> HTML that is the HEAD section of the HTML email.\u003Cbr \u002F>\n– (PHPMailer) \u003Ccode>$mailer\u003C\u002Fcode> The PHPMailer object (by reference).\u003C\u002Fp>\n\u003Cp>Expected return:\u003Cbr \u002F>\n– (string) The altered HEAD section of the HTML email.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>acato_email_essentials_css\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Parameters:\u003Cbr \u002F>\n– (string) \u003Ccode>$the_css\u003C\u002Fcode> CSS for the email (empty by default).\u003Cbr \u002F>\n– (PHPMailer) \u003Ccode>$mailer\u003C\u002Fcode> The PHPMailer object (by reference).\u003C\u002Fp>\n\u003Cp>Expected return:\u003Cbr \u002F>\n– (string) The (altered) CSS.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>acato_email_essentials_minify_css\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Parameters:\u003Cbr \u002F>\n– (string) \u003Ccode>$css\u003C\u002Fcode> CSS to be minified.\u003C\u002Fp>\n\u003Cp>Expected return:\u003Cbr \u002F>\n– (string) The minified CSS.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Mail Throttling\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>acato_email_essentials_mail_is_throttled\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Parameters:\u003Cbr \u002F>\n– (bool) \u003Ccode>$is_throttled\u003C\u002Fcode> Whether the mail is currently throttled.\u003Cbr \u002F>\n– (string) \u003Ccode>$ip\u003C\u002Fcode> The sender’s IP address.\u003Cbr \u002F>\n– (int) \u003Ccode>$mails_recently_sent\u003C\u002Fcode> Number of mails recently sent from this IP.\u003C\u002Fp>\n\u003Cp>Expected return:\u003Cbr \u002F>\n– (bool) Whether the mail should be throttled.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>acato_email_essentials_mail_throttle_time_window\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Parameters:\u003Cbr \u002F>\n– (int) \u003Ccode>$time_window\u003C\u002Fcode> Time window in seconds for counting sent emails.\u003C\u002Fp>\n\u003Cp>Expected return:\u003Cbr \u002F>\n– (int) The (altered) time window in seconds.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>acato_email_essentials_mail_throttle_max_count_per_time_window\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Parameters:\u003Cbr \u002F>\n– (int) \u003Ccode>$count\u003C\u002Fcode> Maximum number of emails allowed per time window.\u003C\u002Fp>\n\u003Cp>Expected return:\u003Cbr \u002F>\n– (int) The (altered) maximum count.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>acato_email_essentials_mail_throttle_batch_size\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Parameters:\u003Cbr \u002F>\n– (int) \u003Ccode>$size\u003C\u002Fcode> Number of emails to send in a single batch.\u003C\u002Fp>\n\u003Cp>Expected return:\u003Cbr \u002F>\n– (int) The (altered) batch size.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>IP Detection\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>acato_email_essentials_ip_services\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Parameters:\u003Cbr \u002F>\n– (array) \u003Ccode>$services\u003C\u002Fcode> The current list of IP services used to determine the sender’s IP address.\u003C\u002Fp>\n\u003Cp>Expected return:\u003Cbr \u002F>\n– (array) The (altered) list of IP services.\u003C\u002Fp>\n\u003Cp>The services must be keyed with \u003Ccode>ipv4\u003C\u002Fcode>, \u003Ccode>ipv6\u003C\u002Fcode> and \u003Ccode>dual-stack\u003C\u002Fcode>. The values must be URLs that return the IP address in plain text.\u003Cbr \u002F>\nThe dual-stack service should return an IPv6 address if available, otherwise an IPv4 address, never both.\u003C\u002Fp>\n\u003Cp>You can set-up your own service like this;\u003C\u002Fp>\n\u003Cul>\n\u003Cli>You will need a webserver that can run PHP, and you need a DNS service that allows you to manually add records.\u003C\u002Fli>\n\u003Cli>You will need three webspaces, for example; ipv4.myservice.com, ipv6.myservice.com and dual-stack.myservice.com.\n\u003Cul>\n\u003Cli>You could use the same webspace for all three, but you will still need three subdomains on the service.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>For the ipv4 subdomain, ONLY register an A record, pointing to the webserver’s IP address.\u003C\u002Fli>\n\u003Cli>For the ipv6 subdomain, ONLY register an AAAA record, pointing to the webserver’s IPv6 address.\u003C\u002Fli>\n\u003Cli>For the dual-stack subdomain, register both an A and an AAAA record, pointing to the webserver’s IP addresses.\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Create a file called \u003Ccode>index.php\u003C\u002Fcode> in each of the webspaces with the following content:\u003C\u002Fp>\n\u003Cp>\u003Ccode>php\u003Cbr \u002F>\n\u003C?php\u003Cbr \u002F>\nheader('Content-Type: text\u002Fplain');\u003Cbr \u002F>\nprint $_SERVER['REMOTE_ADDR'];\u003C\u002Fcode>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>That’s it. You can now use these services in the plugin settings like this;\u003C\u002Fp>\n\u003Cpre>\u003Ccode>`php\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>add_filter(‘acato_email_essentials_ip_services’, ‘my_custom_ip_services’);\u003Cbr \u002F>\nfunction my_custom_ip_services($services) {\u003Cbr \u002F>\n    \u002F\u002F Add your custom services here\u003Cbr \u002F>\n    $services[‘ipv4’] = ‘https:\u002F\u002Fipv4.myservice.com’;\u003Cbr \u002F>\n    $services[‘ipv6’] = ‘https:\u002F\u002Fipv6.myservice.com’;\u003Cbr \u002F>\n    $services[‘dual-stack’] = ‘https:\u002F\u002Fdual-stack.myservice.com’;\u003Cbr \u002F>\n    return $services;\u003Cbr \u002F>\n}\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Cpre>\u003Ccode>acato_email_essentials_ip_service\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Parameters:\u003Cbr \u002F>\n– (string) \u003Ccode>$service\u003C\u002Fcode> The URL of the IP service for the given type.\u003Cbr \u002F>\n– (string) \u003Ccode>$type\u003C\u002Fcode> The type of IP service (‘ipv4’, ‘ipv6’, or ‘dual-stack’).\u003C\u002Fp>\n\u003Cp>Expected return:\u003Cbr \u002F>\n– (string) The (altered) IP service URL.\u003C\u002Fp>\n\u003Cp>Filter to modify individual IP service URLs based on type.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>acato_email_essentials_website_root_path\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Parameters:\u003Cbr \u002F>\n– (string) \u003Ccode>$path\u003C\u002Fcode> The current website root path.\u003C\u002Fp>\n\u003Cp>Expected return:\u003Cbr \u002F>\n– (string) The (possibly altered) website root path.\u003C\u002Fp>\n\u003Cp>Filter to supply the correct website root path in case of non-standard setups.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>acato_email_essentials_development_tlds\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Parameters:\u003Cbr \u002F>\n– (array) \u003Ccode>$tlds\u003C\u002Fcode> Array of top-level domains considered as development environments.\u003C\u002Fp>\n\u003Cp>Expected return:\u003Cbr \u002F>\n– (array) The (altered) array of development TLDs.\u003C\u002Fp>\n\u003Cp>Filter to modify which TLDs are treated as development\u002Flocal environments. Default values are ‘local’ and ‘test’.\u003C\u002Fp>\n\u003Ch3>Scripts\u002Fstyles\u003C\u002Fh3>\n\u003Cp>In the \u003Ccode>public\u002Fscripts\u003C\u002Fcode> and \u003Ccode>public\u002Fstyles\u003C\u002Fcode> folder you find the JS and CSS files used in the plugin admin area.\u003Cbr \u002F>\nThese files are processed with Webpack, just so it works in all recent browsers. Script is nearly identical to the source.\u003C\u002Fp>\n\u003Cp>You can find the source files in the \u003Ccode>src\u002Fscripts\u003C\u002Fcode> and \u003Ccode>src\u002Fstyles\u003C\u002Fcode> folders.\u003C\u002Fp>\n\u003Cp>If you feel the need to modify these files, you can change them there, and run \u003Ccode>npm install ; npm run build\u003C\u002Fcode> to create the production files.\u003C\u002Fp>\n\u003Ch3>Translation files\u003C\u002Fh3>\n\u003Cp>You can use \u003Ccode>npm run i18n\u003C\u002Fcode> to generate the POT file for translation, update the PO files in the \u003Ccode>languages\u003C\u002Fcode> folder, and compile to MO\u002Fphp files.\u003Cbr \u002F>\nThis is a one-task-does-all; run it, change the translations, run it again. Done.\u003Cbr \u002F>\nSee package.json for more details or individual commands.\u003C\u002Fp>\n\u003Ch3>Tools\u003C\u002Fh3>\n\u003Cp>In the \u003Ccode>tools\u003C\u002Fcode> folder you will find a script to generate DKIM keys, should you want to use DKIM signing.\u003Cbr \u002F>\nrename to remove the .txt extension and run it in a shell.\u003C\u002Fp>\n\u003Cp>Tools are provided as-is, without support. Use at your own risk. Read the scripts before using them.\u003C\u002Fp>\n\u003Cp>You DO NOT HAVE TO USE these scripts, you can generate DKIM keys with any tool you like.\u003C\u002Fp>\n\u003Ch3>Arbitrary section\u003C\u002Fh3>\n\u003Cp>For advanced configuration and custom IP services, see the plugin documentation or source code.\u003C\u002Fp>\n","A plugin to make WordPress outgoing emails better and less likely to be marked as spam.",50,235,"2026-03-03T12:44:00.000Z","5.6",[94,95,96,97,98],"deliverability","dkim","email","smime","smtp","https:\u002F\u002Fgithub.com\u002Facato-plugins\u002Femail-essentials","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Femail-essentials.6.0.3.zip",{"slug":102,"name":103,"version":104,"author":5,"author_profile":6,"description":105,"short_description":106,"active_installs":38,"downloaded":107,"rating":38,"num_ratings":38,"last_updated":108,"tested_up_to":25,"requires_at_least":109,"requires_php":110,"tags":111,"homepage":34,"download_link":115,"security_score":49,"vuln_count":38,"unpatched_count":38,"last_vuln_date":61,"fetched_at":40},"block-editor-templates","Block Editor Templates","1.0.7","\u003Cp>WordPress offers the ability to \u003Ca href=\"https:\u002F\u002Fdeveloper.wordpress.org\u002Fblock-editor\u002Freference-guides\u002Fblock-api\u002Fblock-templates\u002F\" rel=\"nofollow ugc\">register block templates for the block editor programmatically\u003C\u002Fa>. This plugin adds a UI to the WP Admin to add block templates without having to be able to program. So if you want every new item of a specific post type to start with a default set of blocks, you can make it happen with this plugin. No programming skills required!\u003C\u002Fp>\n\u003Cp>Furthermore, for classic themes (unfortunately not for block themes), it adds the option to edit the content of post type archives and taxonomy archives.\u003C\u002Fp>\n","Templates for the WordPress Block Editor.",829,"2026-03-09T13:15:00.000Z","5.0","7.2",[112,113,114],"block-templates","block-editor","gutenberg","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fblock-editor-templates.1.0.7.zip"]