Really Simple Security – Simple and Performant Security (formerly Really Simple SSL) vs RS EVENT multiday

Easily improve site security with WordPress Hardening, Two-Factor Authentication (2FA), Login Protection, Vulnerability Detection and SSL certificate. Really simple, Effective and Performant WordPress Security Really Simple Security is the most lightweight and easy-to-use security plugin for WordPress. It secures your WordPress website with SSL certificate generation, including proper 301 https redirection and SSL enforcement, scanning for possible vulnerabilities, Login Protection and implementing essential WordPress hardening features. We believe that security should have the absolute minimum effect on website performance, user experience and maintainability. Therefore, Really Simple Security is: Lightweight: Every security feature is developed with a modular approach and with performance in mind. Disabled features won’t load any redundant code. Easy-to-use: 1-minute configuration with short onboarding setup. Security Features Easy SSL Migration Migrates your website to HTTPS and enforces SSL in just one click. 301 redirect via PHP or .htaccess Secure cookies Let’s Encrypt: Install an SSL Certificate if your hosting provider supports manual installation. Server Health Check: Your server configuration is every bit as important for your website security. WordPress Hardening Tweak your configuration and keep WordPress fortified and safe by tackling potential weaknesses. Prevent code execution in the uploads folder Prevent login feedback and disable user enumeration Disable XML-RPC Disable directory browsing Username restrictions (block ‘admin’ and public names) and much more.. Vulnerability Detection Get notified when plugins, themes or WP core contain vulnerabilities and need appropriate action. Login Protection Allow or enforce Two-Factor Authentication (2FA) for specific user roles. Users receive a two-factor code via Email. Improve Security with Really Simple Security Pro Protect your site with all essential security features by upgrading to Really Simple Security Pro. Advanced SSL enforcement Mixed Content Scan & Fixer. Detect files that are requested over HTTP and fix them to HTTPS, both Front- and Back-end. Enable HTTP Strict Transport Security and configure your site for the HSTS Preload list. Firewall Really Simple Security Pro includes a performant and efficient WordPress firewall, to stop bots, crawlers and bad actors with IP and username blocks. 404 blocking – Blocks crawlers as they trigger unusual numbers of 404 errors. Region blocking – Only allow/block access to your site from specific regions. Automated and customisable Firewall rules. IP blocklist and allowlist. Security Headers Security headers protect your site visitors against the risk of clickjacking, cross-site-forgery attacks, stealing login credentials and malware. Independent of your Server Configuration, works on Apache, LiteSpeed, NGINX, etc. Protect your website visitors with X-XSS Protection, X-Content-Type-Options, X-Frame-Options, a Referrer Policy and CORS headers. Automatically generate your WordPress-tailored Content Security Policy. Vulnerability Measures When a vulnerability is detected in a plugin, theme or WordPress core you will get notified accordingly. With Vulnerability Measures, you can configure simple but effective measures to make sure that a critical vulnerability won’t remain unattended. Force update: An update process will be tried multiple times until it can be assumed development of a theme or plugin is abandoned. You will be notified during these steps. Quarantine: When a plugin or theme can’t be updated to solve a vulnerability, Really Simple Security can quarantine the plugin. Advanced Site Hardening Choose a custom login URL Automated File Permissions check and fixer Rename and randomize your database prefix Change the debug.log file location to a non-public folder Disable application passwords Control admin creation Disable HTTP methods, reducing HTTP requests Login Protection Secure your website’s login process and user accounts with powerful security measures. Two-Step verification (Email login) 2FA (two factor authentication) with TOTP Passwordless login with passkey login Enforce strong passwords and frequent password change Limit Login Attempts With Limit Login Attempts you can configure a threshold to temporarily or permanently block IP addresses or (non-existing) usernames. You can also throw a CAPTCHA after a failed login (hCaptcha or Google reCaptcha) Access Control Restrict access to your site for specific regions. Add specific IP addresses or IP ranges to the Blocklist or Allowlist. Useful Links Documentation Security Definitions Translate Really Simple Security Issues & pull requests Feature requests Love Really Simple Security? If you want to support the continuing development of this plugin, please consider buying Really Simple Security Pro, which includes some excellent security features and premium support. About Really Simple Plugins Our mission is to make complex WordPress requirements really easy. Really Simple Security is developed by Really Simple Plugins. For generating SSL certificates, Really Simple Security uses the le acme2 PHP Let’s Encrypt client library, thanks to ‘fbett’ for providing it. Vulnerability Detection uses WP Vulnerability, an open-source initiative by Javier Casares. Want to join as a collaborator? We’re on GitHub as well!

“RS EVENT multiday” is an easy to use and highly flexible tool to manage and print posts as events by adding the sidebar-widget “RS EVENT multiday” and/or the functions rs_event_list(), rs_event_post() and rs_event_id(), which can be used in templates. It is based on the original “RS EVENT” by Robert Sargant. The plugin offers the possibility to add a “RS EVENT multiday” widget to the sidebar of your blog. It allows you to show a list of upcoming and/or past events. “RS EVENT multiday” includes three different functions, which can be used in templates. rs_event_list(), rs_event_post(), rs_event_id() FUNCTIONS First of all, the “RS EVENT multiday” widget adds the function rs_event_list() to your sidebar and you can costumize all the settings via the widget control panel at the backend of your blog. If you want to create designated pages to show an event list, you should create a special template file for the theme you use and add the function rs_event_list() manually to the code of your template. rs_event_list() This is the function used for the widget. Of course, it can be used in templates as well. It prints an unordered list of events according to the parameters given to it (see below). Both, the and the include class=”rsevent”, so you can costumize the output with stylesheets. Furthermore, the output can be customized with the parameters “html_list_v1”, “html_list_v2”, “html_list_v3” and “html_list_v4”. For details see the parameters-section below. Note: If you just want to get the return values from rs_event_list(), so they do not get printed, you should use the function rs_event_list_return(). rs_event_post() This function should be used in the single-post-template (usually the file single.php of your theme). It prints the date of the event. The output can be customized with the parameters “html_post_v1”, “html_post_v2”, “html_post_v3” and “html_post_v4”. For details see the parameters-section below. Note: If you just want to get the return values from rs_event_post(), so they do not get printed, you should use the function rs_event_post_return(). (This might be useful for e.g. Thematic themes.) rs_event_id() This function returns an array with IDs of posts, which include event-data. This array of IDs can then be used in other functions or loops. Each function can be customized by parameters. PARAMETERS The parameters are used to customize the functions (see above), if you use them within templates. If you use the sidebar-widget of “RS EVENT multiday”, you can make all the settings via the widget control panel at the backend of your blog. Please, have a look at the example below (“How to pass on parameters to one of the functions”) in order to see how it works. title (string) The widget-title in your sidebar. Not used, when the function is added to a template. default value: ‘Upcoming Events’ timespan (integer) The maximum distance into the future events will be retrieved for, in days. default value: 365 history (integer) The maximum distance into the past that events will be retrieved for, in days. This can also be set to a negative negative number, e.g. -2 to prevent events that are occuring in the next two days from appearing. default value: 0 date_format_1 (string) The style in which the date is formatted. date_format_1 is used for single-day events, for the end date of multi-day events, and for the start date of multi-day events if the two dates are NOT within the same year. default value: ‘d.m.Y’ date_format_2 (string) The style in which the date is formatted. date_format_2 is used for the start date of multi-day events if the two dates are within the same year. default value: ‘d.m.’ groupdateformat_y (string) The style in which the yearly headline date is formatted, if events are grouped by year. See also parameter group_by_year. default value: ‘Y’ groupdateformat_m (string) The style in which the monthly headline date is formatted, if events are grouped by month. See also parameter group_by_month. default value: ‘F’ groupdateformat_d (string) The style in which the daily headline date is formatted, if events are grouped by day. See also parameter group_by_day. default value: ‘d, l’ time_format (string) The style in which the time is formatted. Note: ‘second’ cannot be entered for event time and must not be used because of variable $fake_second (used to mark empty time value.) default value: ‘H:i’ time_connector (string) The sign(s) that are printed between the start-time and the end-time, if an end-time is entered. default value: ‘ – ‘ html_list_v1 (string) Used for rs_event_list(). Formats the output, if first date and time of an event is entered with “multi-day”-option off. default value: ‘ %DATE% @ %TIME% | %LOCATION% %TITLE% » read more « ‘ html_list_v2 (string) Used for rs_event_list(). Formats the output, if first date but no time is entered with “multi-day”-option off; if %TIME% is used here anyway (which usually does not make any sense), output of %TIME% equals “–:–“. default value: ‘ %DATE% | %LOCATION% %TITLE% » read more « ‘ html_list_v3 (string) Used for rs_event_list(). Formats the output, if “multi-day”-option is on and first date and end date is entered. default value: ‘ %DATE% - %ENDDATE% | %LOCATION% %TITLE% » read more « ‘ html_list_v4 (string) Used for rs_event_list(). Formats the output, if “multi-day”-option is on but no end date is entered. default value: ‘ %DATE% (multi-day) | %LOCATION% %TITLE% » read more « ‘ html_post_v1 (string) Used for rs_event_post(). Formats the output, if first date and time of an event is entered with “multi-day”-option off. default value: ‘ %DATE% @ %TIME% ‘ html_post_v2 (string) Used for rs_event_post(). Formats the output, if first date but no time is entered with “multi-day”-option off; if %TIME% is used here anyway (which usually does not make any sense), output of %TIME% equals “–:–“. default value: ‘ %DATE% ‘ html_post_v3 (string) Used for rs_event_post(). Formats the output, if “multi-day”-option is on and first date and end date is entered. default value: ‘ %DATE% - %ENDDATE% ‘ html_post_v4 (string) Used for rs_event_post(). Formats the output, if “multi-day”-option is on but no end date is entered. default value: ‘ %DATE% (multi-day event) ‘ max_events (integer) The maximum number of events to show. If this is set to 0, then all events will be shown. default value: 0 (i.e. show all) group_by_year (integer) value 0 = off, value 1 = on. If group_by_year is set, the function rs_event_list() outputs a date as a headline for all events, that take place within the same year. For multiday events, the first day of the event is used for grouping and every event shows up only once. The format of the date can be set with the parameter groupdateformat_y default value: 0 (i.e. “off”) group_by_month (integer) value 0 = off, value 1 = on. If group_by_month is set, the function rs_event_list() outputs a date as a headline for all events, that take place within the same month. For multiday events, the first day of the event is used for grouping and every event shows up only once. The format of the date can be set with the parameter groupdateformat_m default value: 0 (i.e. “off”) group_by_day (integer) value 0 = off, value 1 = on. If group_by_day is set, the function rs_event_list() outputs a date as a headline for all events, that take place within the same day. For multiday events, the first day of the event is used for grouping and every event shows up only once. The format of the date can be set with the parameter groupdateformat_y default value: 0 (i.e. “off”) no_events_msg (string) The output when the are no events within the set timespan. default value: ‘no upcoming events’ sort_order (string) Whether to list the events in ascending (value: ‘ASC’) or descending (value: ‘DESC’) date order. default value: ‘ASC’ category (integer) Show only events listed against posts in the category with this ID number. If this is set to 0, then all events will be shown. default value: 0 (i.e. show all) fulltext_active (integer) If this is set to 0, the wildcard %FULLTEXT% cannot be used for the HTML-Output of the Event-List and an excerpt for the wildcard %EXCERPT% is not created automatically, consequently, it has to be entered via the excerpt-box at the edit-post-page. You should disable %FULLTEXT% and set this to 0, if you do not need or use %FULLTEXT% and if you manually creat excerpts in order to improve the perfomance of the plugin RS EVENT multiday. default value: 1 (i.e. enabled and %FULLTEXT% can be used and excerpts are created automatically) loggedin (integer) Allows to hide the widget or the output of the function rs_event_list(). If this is set to 0, the list or the widget will only be visible to logged in users. default value: 0 (i.e. widget and function are visible to all) Customizing the html-output with wildcards The values “html_list_vX” and “html_post_vX” can be styled both for the widget (-> via the widget control panel) and within templates (please have a look at the example “How to pass on parameters to one of the functions” below). Simply use html-code and the following parameters: %URL% Outputs the URL of the event-post. %DATE% Outputs the start-date of the event, formatted as date_format_1 in _v1, _v2 and _v4 and as date_format_2 in _v3. %ENDDATE% Outputs the end-date of the event, formatted as date_format_2. %TIME% If a starttime and endtime is entered, the output is similar to %STARTTIME% time-connector %ENDTIME%. If just a starttime and no endtime is entered, %TIME% is similar to %STARTTIME%. %STARTTIME% Outputs the time when the event starts, if one is entered, formatted as time_format. %ENDTIME% Outputs the time when the event ends, if one is entered (can only be entered if a starttime exists), formatted as time_format. %LOCATION% Outputs an ordinary text value (if one is entered) which might be used to enter e.g. the location of the event. %TITLE% Outputs the title of the post. %FULLTEXT% Outputs the entire text of the post. (You can disable this wildcard to improve the perfomance of the plugin.) %EXCERPT% Outputs the excerpt of the post. If the %FULLTEXT% wildcard is disabled, an excerpt is not created automatically. Consequently, the excerpt-box at the edit-post-page has to be filled with text in order to output an excerpt when %FULLTEXT% is disabled. Please, also see the information for “fulltext_active” at the parameter section above. %ID% Outputs the ID of the post. How to pass on parameters to one of the functions Here is an example how to pass on some parameters to the function rs_event_list() [or rs_event_list_return()], when used within a template. It works similar with rs_event_post() [and rs_event_post_return()], just use the html_post_vX parameters instead of the html_list_vX parameters. Note: Parameters for the widget can be simply passed via the Widget-Panel of your blog-backend. 60, 'date_format_1' => 'm|d|Y', 'date_format_2' => 'm|d', 'html_list_v1' => ' %DATE%, %TIME% %TITLE% ', 'html_list_v2' => ' %DATE% %TITLE% ', 'html_list_v3' => ' %DATE% to %ENDDATE% %TITLE% ', 'html_list_v4' => ' %DATE% (multiday!!!) %TITLE% ', 'max_events' => 4, ); rs_event_list($argsevent); ?>