[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f7c6dCC5wKg0FiMZDMElZZiQV6QxodxspnupNezgDsEE":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},"awelzel","Arno Welzel","https:\u002F\u002Fprofiles.wordpress.org\u002Fawelzel\u002F",5,29340,100,364,79,"2026-05-20T05:44:24.004Z",[14,39,58,77,93],{"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},"lightbox-photoswipe","Lightbox with PhotoSwipe","5.8.3","\u003Cp>This plugin integrates PhotoSwipe to WordPress. All linked images in a post or page will be displayed using PhotoSwipe, regardless if they are part of a gallery or single images.\u003C\u002Fp>\n\u003Cp>More about the original version of PhotoSwipe see here: \u003Ca href=\"http:\u002F\u002Fphotoswipe.com\" rel=\"nofollow ugc\">http:\u002F\u002Fphotoswipe.com\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>You can also display EXIF data from supported image types.\u003C\u002Fp>\n\u003Cp>As of version 4.0.0 this plugin requires at least WordPress 5.3 and PHP 7.0. Older PHP version will cause problems. In this case you have to upgrade your PHP version or ask your hoster to do so. Please note that WordPress itself also recommends at least PHP 7.4 – see \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fabout\u002Frequirements\u002F\" rel=\"ugc\">https:\u002F\u002Fwordpress.org\u002Fabout\u002Frequirements\u002F\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Please keep in mind: not the visible thumbnail is relevant, but only the image link. Images should always be linked to the file and not to the attachment page. Since version 5.6.1 there is an option to fix attachment links which can be enabled if needed – however this may slow down your website since then all links on a page will be checked if they are attachment links.\u003C\u002Fp>\n","Integration of PhotoSwipe (http:\u002F\u002Fphotoswipe.com) for WordPress.",20000,942475,98,114,"2026-02-26T16:27:00.000Z","6.9.4","5.3","",[29,30,31,32,33],"attachments","gallery","images","lightbox","photoswipe","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Flightbox-photoswipe\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flightbox-photoswipe.5.8.3.zip",0,null,"2026-04-16T10:56:18.058Z",{"slug":40,"name":41,"version":42,"author":5,"author_profile":6,"description":43,"short_description":44,"active_installs":45,"downloaded":46,"rating":47,"num_ratings":48,"last_updated":49,"tested_up_to":25,"requires_at_least":50,"requires_php":27,"tags":51,"homepage":54,"download_link":55,"security_score":9,"vuln_count":56,"unpatched_count":36,"last_vuln_date":57,"fetched_at":38},"timed-content","Timed Content","2.97","\u003Cp>The Timed Content plugin allows users to specify that a portion of a Page or Post should appear\u002Fbe visible or disappear\u002Fbe invisible based on given time characteristics. You can also make portions of a Post or Page be visible at certain dates and times; you can even set up a schedule!\u003C\u002Fp>\n\u003Cp>The plugin adds the following:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A “client-side” shortcode that allows the marking of content to appear or disappear after a given time interval; a “fade” effect is included.  This functionality is intended to be used for special effects only, as content marked in this manner is still visible in the HTML source and, therefore, not a secure method of hiding content.\u003C\u002Fli>\n\u003Cli>Two “server-side” shortcodes that allow the marking of content to be visible only during specified date\u002Ftime intervals.  This functionality \u003Cstrong>can\u003C\u002Fstrong> be used as a secure method of hiding content, because the marked content will be included in the Page\u002FPost \u003Cstrong>only\u003C\u002Fstrong> when viewed in the specified date\u002Ftime intervals.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>A TinyMCE dialog is included to help users build the shortcodes. See the Screenshots tab for more info.\u003C\u002Fp>\n\u003Ch3>Examples\u003C\u002Fh3>\n\u003Cpre>\u003Ccode>[timed-content-client show=\"1:00\"]Show me after one minute.  Since we don't want a fade-in, we can leave it out of the \"show\" attribute completely.[\u002Ftimed-content-client]\n\n[timed-content-client show=\"1:00:1000\"]Show me after one minute with a 1000 millisecond (1 second) fade-in.[\u002Ftimed-content-client]\n\n[timed-content-client hide=\"1:00:1000\"]Hide me after one minute with a 1000 millisecond (1 second) fade-out.[\u002Ftimed-content-client]\n\n[timed-content-client show=\"1:00:500\" hide=\"5:00:2000\"]Show me after one minute with a 500 millisecond (a half-second) fade-in, then hide me after five minutes with a 2000 millisecond (2 seconds) fade-out.[\u002Ftimed-content-client]\n\n[timed-content-server show=\"2013-09-13 20:30:00 -0600\"]Show me starting at 8:30 PM Central Standard Time on September 13th, 2013. I will not be displayed before then.[\u002Ftimed-content-server]\n\n[timed-content-server hide=\"2013-09-13 20:30:00 America\u002FChicago\"]Hide me starting at 8:30 PM Central Daylight Time (i.e., the same timezone as Chicago) on September 13th, 2013.  I will not be displayed after then[\u002Ftimed-content-server]\n\n[timed-content-server show=\"2013-09-13 20:30:00 -0600\" hide=\"2013-09-13 21:30:00 -0600\"]Show me starting at 8:30 PM Central Standard Time on September 13th, 2013, then hide me an hour later. I will not be displayed before or after then.[\u002Ftimed-content-server]\n\n[timed-content-rule id=\"164\"]Display me based on the settings for the Timed Content Rule whoseID is 164.[\u002Ftimed-content-rule]\u003Ch3>Usage\u003C\u002Fh3>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>NOTE: All shortcodes can be built using the TinyMCE dialog.  When in doubt, use the dialog to create correctly formed shortcodes.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>The timed-content-client shortcode\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[timed-content-client show=\"mm:ss:fff\" hide=\"mm:ss:fff\"]Example Text[\u002Ftimed-content-client]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cul>\n\u003Cli>\u003Ccode>show\u003C\u002Fcode> – Specifies the time interval after loading the web page when the marked content should be displayed. The attribute consists of three parts,\u003Cbr \u002F>\nseparated by colons: \u003Ccode>mm\u003C\u002Fcode> – minutes, \u003Ccode>ss\u003C\u002Fcode> – seconds, and \u003Ccode>fff\u003C\u002Fcode> – if greater than \u003Ccode>0\u003C\u002Fcode>, a fade-in effect lasting \u003Ccode>fff\u003C\u002Fcode> milliseconds is applied.\u003C\u002Fli>\n\u003Cli>\u003Ccode>hide\u003C\u002Fcode> – Specifies the time interval after loading the web page when the marked content should be hidden. The attribute consists of three parts,\u003Cbr \u002F>\nseparated by colons: \u003Ccode>mm\u003C\u002Fcode> – minutes, \u003Ccode>ss\u003C\u002Fcode> – seconds, and \u003Ccode>fff\u003C\u002Fcode> – if greater than \u003Ccode>0\u003C\u002Fcode>, a fade-out effect lasting \u003Ccode>fff\u003C\u002Fcode> milliseconds is applied.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Both attributes are optional, but at least one attribute must be included. Leading zeros (0) are optional. The shortcode’s behaviour depends on which attributes are used:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>show\u003C\u002Fcode> only – Marked content is initially not visible, then appears \u003Ccode>mm\u003C\u002Fcode> minutes and \u003Ccode>ss\u003C\u002Fcode> seconds after loading with a \u003Ccode>fff\u003C\u002Fcode> millisecond fade-in.\u003C\u002Fli>\n\u003Cli>\u003Ccode>hide\u003C\u002Fcode> only – Marked content is initially visible, then disappears \u003Ccode>mm\u003C\u002Fcode> minutes and \u003Ccode>ss\u003C\u002Fcode> seconds after loading with a \u003Ccode>fff\u003C\u002Fcode> millisecond fade-out.\u003C\u002Fli>\n\u003Cli>\u003Ccode>show\u003C\u002Fcode> and \u003Ccode>hide\u003C\u002Fcode> – Marked content is initially not visible, then appears according to the values set in \u003Ccode>show\u003C\u002Fcode>, then disappears according to the values set in \u003Ccode>hide\u003C\u002Fcode>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Your users must have JavaScript enabled for this shortcode to work.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>The timed-content-server shortcode\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[timed-content-server show=\"datetime\" hide=\"datetime\" debug=\"true|false|when_hidden\"]Example Text[\u002Ftimed-content-server]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cul>\n\u003Cli>\u003Ccode>show\u003C\u002Fcode> – Specifies the date\u002Ftime when the marked content should start being included on the web page.\u003C\u002Fli>\n\u003Cli>\u003Ccode>hide\u003C\u002Fcode> – Specifies the date\u002Ftime after which the marked content should stop being included on the web page.\u003C\u002Fli>\n\u003Cli>\u003Ccode>debug\u003C\u002Fcode> – If \u003Ccode>true\u003C\u002Fcode>, adds some debugging statements to the web page as HTML comments. If \u003Ccode>when_hidden\u003C\u002Fcode>, the debugging statements are added only when the content is hidden. Defaults to \u003Ccode>false\u003C\u002Fcode>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The date and time are expected to be yyyy-mm-dd HH:MM (similar to ISO 8601), for example \u003Ccode>2019-04-07 15:30\u003C\u002Fcode> for April 7, 2019, 15:30. For backward compatiblity old “human readable” date formats should also work, but these should not be used any longer!\u003C\u002Fp>\n\u003Cp>In addition you can provide a timezone in the date\u002Ftime parameter either as name or as offset like \u003Ccode>2019-04-07 15:30 America\u002FChicago\u003C\u002Fcode> or \u003Ccode>2019-04-07 15:30 +0200\u003C\u002Fcode>. If you do not provide a timezone, the WordPress timezone setting will be used as default.\u003C\u002Fp>\n\u003Cp>Both \u003Ccode>show\u003C\u002Fcode> and \u003Ccode>hide\u003C\u002Fcode> attributes are optional, but at least one attribute must be included. The shortcode’s behaviour depends on which attributes are used:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>show\u003C\u002Fcode> only – Marked content is outputted only after the date\u002Ftime set here.\u003C\u002Fli>\n\u003Cli>\u003Ccode>hide\u003C\u002Fcode> only – Marked content is outputted only before the date\u002Ftime set here.\u003C\u002Fli>\n\u003Cli>\u003Ccode>show\u003C\u002Fcode> and \u003Ccode>hide\u003C\u002Fcode> – Marked content is outputted only during the time period defined by the \u003Ccode>show\u003C\u002Fcode> and \u003Ccode>hide\u003C\u002Fcode> attributes.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>The timed-content-rule shortcode\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[timed-content-rule id=\"{rule_id}|{rule_name}\"]Example Text[\u002Ftimed-content-rule]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>You can find the correct shortcode from the Timed Content Rules overview page, or use the TinyMCE dialog.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Testing server side rules\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>For testing the behaviour of server side rules at specific times, you may use the GET parameter \u003Ccode>tctest\u003C\u002Fcode> in an URL, followed by date and time in the format \u003Ccode>YYYY-MM-DD+hh:mm:ss\u003C\u002Fcode>. This works only you are logged in with a user which has the right to edit the displayed page or post. For example: \u003Ccode>http:\u002F\u002Fmysite.example?tctest=2018-02-10+19:16:00\u003C\u002Fcode> will show the content as if it was February 10, 2018 at 19:16.\u003C\u002Fp>\n\u003Ch3>Developer Documentation\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Action hooks\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_action( \"timed_content_server_show\", \"{function_name}\", {priority_level}, 4 );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Fired when the \u003Ccode>[timed-content-server]\u003C\u002Fcode> shortcode is encountered \u003Cem>AND\u003C\u002Fem> the content is to be displayed based on the shortcode’s show\u002Fhide attributes.  Functions using this hook should accept the following arguments in order:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>$post_id\u003C\u002Fcode> – the ID of the currently displayed Post\u002FPage\u003C\u002Fli>\n\u003Cli>\u003Ccode>$show\u003C\u002Fcode> – the value of the \u003Ccode>show\u003C\u002Fcode> attribute. If not set, defaults to “1970-Jan-01 00:00:00 +000”\u003C\u002Fli>\n\u003Cli>\u003Ccode>$hide\u003C\u002Fcode> – the value of the \u003Ccode>hide\u003C\u002Fcode> attribute. If not set, defaults to “2038-Jan-19 03:14:07 +000”\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>$content\u003C\u002Fcode> – The content enclosed by the shortcode\u003C\u002Fp>\n\u003Cp>add_action( “timed_content_server_hide”, “{function_name}”, {priority_level}, 4 );\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Fired when the \u003Ccode>[timed-content-server]\u003C\u002Fcode> shortcode is encountered \u003Cem>AND\u003C\u002Fem> the content is to be hidden based on the shortcode’s show\u002Fhide attributes.  Functions using this hook should accept the following arguments in order:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>$post_id\u003C\u002Fcode> – the ID of the currently displayed Post\u002FPage\u003C\u002Fli>\n\u003Cli>\u003Ccode>$show\u003C\u002Fcode> – the value of the \u003Ccode>show\u003C\u002Fcode> attribute. If not set, defaults to “1970-Jan-01 00:00:00 +000”\u003C\u002Fli>\n\u003Cli>\u003Ccode>$hide\u003C\u002Fcode> – the value of the \u003Ccode>hide\u003C\u002Fcode> attribute. If not set, defaults to “2038-Jan-19 03:14:07 +000”\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>$content\u003C\u002Fcode> – The content enclosed by the shortcode\u003C\u002Fp>\n\u003Cp>add_action( “timed_content_rule_show”, “{function_name}”, {priority_level}, 3 );\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Fired when the \u003Ccode>[timed-content-rule]\u003C\u002Fcode> shortcode is encountered \u003Cem>AND\u003C\u002Fem> the content is to be displayed based on the Timed Content Rule’s properties.  Functions using this hook should accept the following arguments in order:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>$post_id\u003C\u002Fcode> – the ID of the currently displayed Post\u002FPage\u003C\u002Fli>\n\u003Cli>\u003Ccode>$rule_id\u003C\u002Fcode> – the ID of the Timed Content Rule being called. Use \u003Ccode>get_post_meta( $rule_id )\u003C\u002Fcode> to get the Rule’s properties.\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>$content\u003C\u002Fcode> – The content enclosed by the shortcode\u003C\u002Fp>\n\u003Cp>add_action( “timed_content_rule_hide”, “{function_name}”, {priority_level}, 3 );\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Fired when the \u003Ccode>[timed-content-rule]\u003C\u002Fcode> shortcode is encountered \u003Cem>AND\u003C\u002Fem> the content is to be hidden based on the Timed Content Rule’s properties.  Functions using this hook should accept the following arguments in order:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>$post_id\u003C\u002Fcode> – the ID of the currently displayed Post\u002FPage\u003C\u002Fli>\n\u003Cli>\u003Ccode>$rule_id\u003C\u002Fcode> – the ID of the Timed Content Rule being called. Use \u003Ccode>get_post_meta( $rule_id )\u003C\u002Fcode> to get the Rule’s properties.\u003C\u002Fli>\n\u003Cli>\u003Ccode>$content\u003C\u002Fcode> – The content enclosed by the shortcode\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Filter hooks\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>timed_content_filter\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Filter for any content enclosed by a Timed Content shortcode.  Implements the same filters as \u003Ccode>the_content\u003C\u002Fcode>:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>wptexturize\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>convert_smilies\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>convert_chars\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>wpautop\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>prepend_attachment\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>do_shortcode\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cp>timed_content_filter_override\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Replaces the \u003Ccode>timed_content_filter\u003C\u002Fcode> with another pre-existing filter to use for any content enclosed by a Timed Content shortcode.  Any function hooked into this filter must return the name of a filter (as a string).\u003C\u002Fp>\n","Plugin to show or hide portions of a Page or Post based on specific date\u002Ftime characteristics.",6000,220010,92,41,"2025-12-02T23:43:00.000Z","3.8",[52,53,40],"marketing-tool","schedule","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Ftimed-content\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ftimed-content.2.97.zip",1,"2023-01-24 00:00:00",{"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":25,"requires_at_least":69,"requires_php":27,"tags":70,"homepage":75,"download_link":76,"security_score":9,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"comment-reply-email-notification","Comment Reply Email Notification","1.39.0","\u003Cp>This plugin allows visitors to subscribe to get answers to their comments via e-mail.\u003C\u002Fp>\n\u003Ch3>Warning\u003C\u002Fh3>\n\u003Cp>This plugin uses the “wp_insert_comment” hook, therefore, everytime a comment is created, a notification is likely to be sent. If you are importing comments into your blog, it’s a good idea to disable this plugin.\u003C\u002Fp>\n\u003Ch3>Sending e-mails does not work?\u003C\u002Fh3>\n\u003Cp>The plugin uses the standard WordPress e-mail function. If you have problems getting e-mails sent, you might try using plugins like https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-mail-smtp\u002F to improve sending e-mails from your site.\u003C\u002Fp>\n\u003Ch3>Customizing the layout of the checkboxes\u003C\u002Fh3>\n\u003Cp>The label next to the checkboxes don’t contain a whitespace. Depending on your theme you might want to add a custom style like this to get a space between the checkbox and the label:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>input#cren_subscribe_to_comment, input#cren_gdpr {\n  margin-right: 0.5em;\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The plugin does not add this style be default as it depends on your theme if this is neccessary.\u003C\u002Fp>\n\u003Ch3>Customizing the email template\u003C\u002Fh3>\n\u003Cp>To customize the email template, copy the “templates” folder to your theme folder (a child theme should be used to avoid losing the custom templates when the theme is updated). The plugin will look for templates on the “\u002Fwp-content\u002Fthemes\u002F[THEME]\u002Ftemplates\u002Fcren\u002F” folder; if a custom template is not found, then it will fallback to the default template.\u003C\u002Fp>\n\u003Cp>Templates folder on GitHub: https:\u002F\u002Fgithub.com\u002Farnowelzel\u002Fworpdress-comment-reply-email-notification\u002Ftree\u002Fmaster\u002Ftemplates\u003C\u002Fp>\n\u003Ch3>Changing the subscription checkbox label\u003C\u002Fh3>\n\u003Cp>The checkbox label can be changed with the \u003Ccode>cren_comment_checkbox_label\u003C\u002Fcode> filter. This way you can update the text to your taste and keep the plugin updated.\u003C\u002Fp>\n\u003Ch3>Changing the GDPR checkbox label\u003C\u002Fh3>\n\u003Cp>The GDPR checkbox label can be changed with the \u003Ccode>cren_gdpr_checkbox_label\u003C\u002Fcode> filter. This way you can update the text to your taste and keep the plugin updated.\u003C\u002Fp>\n\u003Ch3>Modifiying HTML output\u003C\u002Fh3>\n\u003Cp>Using the filters \u003Ccode>cren_gdpr_checkbox_html\u003C\u002Fcode> and \u003Ccode>cren_comment_subscribe_html\u003C\u002Fcode> you can modify the HTML output of the checkboxes if needed.\u003C\u002Fp>\n\u003Cp>Example:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_filter('cren_gdpr_checkbox_html', function(string $html_output, string $label_text, string $privacy_policy_url): string {\n    $html_output = '\u003Cdiv class=\"comment-form-gdpr-consent form-check mb-3\">\u003Cinput id=\"cren_gdpr\" class=\"form-check-input\" name=\"cren_gdpr\" type=\"checkbox\" value=\"yes\" required checked>\u003Clabel for=\"cren_gdpr\" class=\"form-check-label\">' . $label_text . '\u003Cspan class=\"text-danger fw-bold\">*\u003C\u002Fspan> (\u003Ca href=\"' . $privacy_policy_url . '\" title=\"Privacy Policy\" target=\"_blank\" rel=\"internal\">Privacy Policy\u003C\u002Fa>)\u003C\u002Flabel>\u003C\u002Fdiv>';\n\n    return $html_output;\n}, 10, 3);\n\nadd_filter('cren_comment_subscribe_html', function(string $html_output, string $label_text, bool $checked_default): string {\n    $checked = $checked_default ? 'checked' : '';\n    $html_output = '\u003Cdiv class=\"comment-form-email-consent form-check mb-3\">\u003Cinput id=\"cren_subscribe_to_comment\" class=\"form-check-input\" name=\"cren_subscribe_to_comment\" type=\"checkbox\" value=\"on\" ' . $checked . '>\u003Clabel for=\"cren_subscribe_to_comment\" class=\"form-check-label\">' . $label_text . '\u003C\u002Flabel>\u003C\u002Fdiv>';\n\n    return $html_output;\n}, 10, 3);\n\u003C\u002Fcode>\u003C\u002Fpre>\n","This plugin allows visitors to subscribe to get answers to their comments via e-mail.",3000,107546,96,32,"2025-12-13T08:26:00.000Z","4.4.0",[71,72,73,74],"comment","email","notification","reply","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcomment-reply-email-notification\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcomment-reply-email-notification.1.39.0.zip",{"slug":78,"name":79,"version":80,"author":5,"author_profile":6,"description":81,"short_description":82,"active_installs":83,"downloaded":84,"rating":85,"num_ratings":7,"last_updated":86,"tested_up_to":25,"requires_at_least":87,"requires_php":27,"tags":88,"homepage":91,"download_link":92,"security_score":9,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"multicolumn-category-widget","Multicolumn Category Widget","1.0.27","\u003Cp>This widget displays top level categories in multiple columns.\u003C\u002Fp>\n\u003Cp>After installation, just add the widget to desired sidebar or footer and optionally enter a custom title and the number of columns to be displayed.\u003C\u002Fp>\n\u003Cp>By default two columns are used, but you can set any number of columns you like in the backend.\u003C\u002Fp>\n\u003Cp>Also see details at \u003Ca href=\"http:\u002F\u002Farnowelzel.de\u002Fwp\u002Fen\u002Fprojects\u002Fwordpress\u002Fmulticolumn-category-widget\" rel=\"nofollow ugc\">http:\u002F\u002Farnowelzel.de\u002Fwp\u002Fen\u002Fprojects\u002Fwordpress\u002Fmulticolumn-category-widget\u003C\u002Fa>.\u003C\u002Fp>\n","This widget displays top level categories in multiple columns.",300,17603,84,"2025-12-14T12:51:00.000Z","3.6",[89,90],"category","widget","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fmulticolumn-category-widget\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmulticolumn-category-widget.1.0.27.zip",{"slug":94,"name":95,"version":96,"author":5,"author_profile":6,"description":97,"short_description":98,"active_installs":99,"downloaded":100,"rating":36,"num_ratings":36,"last_updated":101,"tested_up_to":25,"requires_at_least":102,"requires_php":27,"tags":103,"homepage":27,"download_link":105,"security_score":9,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":106},"webstats-matomo","Website statistics with Matomo","1.28","\u003Cp>This plugin allows to use a self hosted Matomo server to get website statistics. When enabled, the neccessary code is added to the footer of the website. There is also a direct link to your Matomo server in the WordPress dashboard.\u003C\u002Fp>\n\u003Cp>Proxy integration based on the code by Stefan Giehl, also see \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fmatomo-org\u002Ftracker-proxy\" rel=\"nofollow ugc\">https:\u002F\u002Fgithub.com\u002Fmatomo-org\u002Ftracker-proxy\u003C\u002Fa>.\u003C\u002Fp>\n","Integration of statistics provided by Matomo for WordPress.",40,4999,"2025-12-12T20:05:00.000Z","4.0",[104],"statistics","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwebstats-matomo.1.28.zip","2026-04-06T09:54:40.288Z"]