jammycakes

This plugin extends the comment closing functionality in WordPress to allow 
you to extend the discussion time when older posts have recent comments 
accepted, or to override the comment closing time on a post by post basis.
Note: PHP 4 is no longer supported. As of version 2.1, Comment Timeout requires PHP 5.2 or later. 
If you are still using PHP 4, you should use Comment Timeout 2.0.1.
<h3>Configuration</h3>
You can change various settings globally on the “Comment Timeout” page under the 
“Options” tab on the WordPress dashboard. Most of the options are fairly 
self-explanatory.
You can also change options on a per-post basis by looking for the 
“Comment Timeout” section in the sidebar of the post or page editor.
<h3>Template tags</h3>
Comment Timeout 2.1 introduces two new functions that you can use in your theme:
<pre><code>get_comment_timeout()
</code></pre>
Returns the UTC time, as a Unix timestamp, when comments will be closed for the current post.
<pre><code>the_comment_timeout($relative, $dateformat, $before, $after, $moderated)
</code></pre>
Formats and displays the date and time after which comments will no longer be 
accepted on this post. Parameters are:
<ul>
<li>$relative: Set this to <code>true</code> if you want to display the date in terms of the time remaining 
(for instance “in 3 weeks”). Set it to <code>false</code> to display it as an absolute date.</li>
<li>$dateformat: The format in which the date should be displayed, as used by the PHP 
date() function. If you set this to <code>false</code>, it will use the date format that you have configured 
globally for your WordPress installation.
<ul>
<li>If <code>$relative</code> is set to <code>true</code>, this parameter is ignored.</li>
</ul>
</li>
<li>$before: The HTML to insert before the date that comments will be closed.</li>
<li>$after: The HTML to insert after the date that comments will be closed.</li>
<li>$moderated: The HTML to display when late comments are being sent to the moderation queue 
rather than being rejected outright.</li>
</ul>
<h3>Development and reporting bugs</h3>
When reporting bugs, please provide me with the following information:
<ol>
<li>Which version of Comment Timeout you are using;</li>
<li>Which version of WordPress you are using;</li>
<li>The URL of your blog;</li>
<li>Which platform (Windows/IIS/PHP or Linux/Apache/MySQL/PHP) your server 
is running, and which versions of Apache and PHP you are using, if you 
know them;</li>
<li>The steps that need to be taken to reproduce the bug.</li>
</ol>
If you wish to get hold of the latest development version, or to contribute 
bug fixes or new features, you can clone the project on GitHub:
<pre><code>git clone git@github.com:jammycakes/comment-timeout.git<h3>Redistribution</h3>
</code></pre>
Copyright (c) 2007-2013 James McKay 
http://jamesmckay.net/
Permission is hereby granted, free of charge, to any person obtaining a copy 
of this software and associated documentation files (the “Software”), to deal 
in the Software without restriction, including without limitation the rights 
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 
copies of the Software, and to permit persons to whom the Software is 
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in 
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 
SOFTWARE.
<h3>For more information</h3>
For more information, please visit the plugin’s home page:
https://github.com/jammycakes/comment-timeout

Comment Timeout

Closes comments on blog entries after a user-configurable period of time, with an option to make allowances for active discussions.

Pascal

iQ Block Country is a plugin that allows you to limit access to your website content. You can either allow or disallow visitors from defined countries to (parts of) your content.
For instance if you have content that should be restricted to a limited set of countries you can do so. 
If you want to block rogue countries that cause issues like for instance hack attempts, spamming of your comments etc you can block them as well.
Do you want secure your WordPress Admin backend site to only your country? Entirely possible! You can even block all countries and only allow your ip address.
And even if you block a country you can still allow certain visitors by putting their ip address on the allow list just like you can allow a country but put ip addresses on the block list from that country.
You can show blocked visitors a message which you can style by using CSS or you can redirect them to a page within your WordPress site. Or you can redirect the visitors to an external website.
You can (dis)allow visitors to blog articles, blog categories or pages or all content.
Stop visitors from doing harmful things on your WordPress site or limit the countries that can access your blog. Add an additional layer of security to your WordPress site.
This plugin uses the GeoLite database from Maxmind. It has a 99.5% accuracy so that is pretty good for a free database. If you need higher accuracy you can buy a license from MaxMind directly. 
If you cannot or do not want to download the GeoIP database from Maxmind you can use the GeoIP API website available on https://webence.net/ 
If you want to use the GeoLite database from Maxmind you will have to download the GeoIP database from MaxMind directly and upload it to your site. 
The WordPress license does not allow this plugin to download the MaxMind Geo database for you.
Please be aware that although this plugin can help you greatly with reducing the number of ‘bad’ visitors on your website it is not fool proof and those who really want to visit your site may find a away. 
This is not a security issue but a simple fact of today. Nobody can guarantee you 100% security as it is a constant battle between the good guys and the bad guys.
If you are sure your webhosting or yourself does not use any form of caching or proxying we recommend setting the “Override IP information” on the Home tab to REMOTE_ADDR
Do you need help with this plugin? Please email support@webence.net.
<h4>GDPR Information</h4>
This plugin stores data about your visitors in your local WordPress database. The number of days this data is stores can be configured on the settings page. You can also disable logging any data.
Data which is stored of blocked visitors:
<ul>
<li>IP Address</li>
<li>Date and time of the visit</li>
<li>URL that was requested</li>
<li>Country of the IP address</li>
<li>If the block happened on your backend or your frontend</li>
</ul>
Data which is stored on non blocked visitors:
<ul>
<li>Nothing</li>
</ul>
If you allow tracking (yeah if you do!) you share some information with us. This is only the IP address of a blocked request on your backend. No other information is send and only the IP address is logged on our systems to gather how many times that IP address have attempted to login to a backend. We do not log which site was visited or which URL just only the IP address So we cannot lead an ip address back to a specific website or user. If an IP address is not blocked again within a month we will remove the IP address from the list.
If you use the GeoIP API service you send the IP address of your visitor to one of our servers. This IP Address is however in no way stored at our servers and only used to convert it to a country id.
<h4>Using this plugin with a caching plugin</h4>
Please note that many of the caching plugins are not compatible with this plugin. The nature of caching is that a dynamically build web page is cached into a static page. 
 If a visitor is blocked this plugin sends header data where it supplies info that the page should not be cached. Many plugins however disregard this info and cache the page or the redirect. Resulting in valid visitors receiving a message that they are blocked. This is not a malfunction of this plugin.
Disclaimer: No guarantees are made but after some light testing the following caching plugins seem to work: Comet Cache, WP Super Cache 
Plugins that do NOT work: W3 Total Cache, Hyper cache, WPRocket
Warning: Caching & Geo Blocking do not work well together.
In the best case scenario countries or IP’s you want to block get served a page from cache and when visiting non cached pages they get blocked. This is due to the fact when pages are served from cache the iQ Block Country plugin does not get started and can’t do it’s job.
If the caching plugin however ignores the caching headers you risk the chance that the block message gets cached and everyone gets to see they are blocked even the countries that you did not block.
If you’re fine with blocked countries getting served the page from cache then you’re fine using the iQ Block Country plugin.
If you’re not you should disable either the cache or the Geo Blocking. Or search for another solution outside WordPress (for instance by using the Varnish software) where you can GeoBlock at a caching level.
<h3>GeoIP API</h3>
For your convenience we offer a GeoIP API service. This API is not mandatory to use as you can always use the free MaxMind GeoIP Database.
If you do not want or can’t go through the hassle of updating your MaxMind GeoIP database we provide an API service to convert the IP address of your visitors to a country.
If you decide to purchase an GeoIP API Key via https://webence.net you’ll get an eMail with your API Key (License Key). 
Once you enter this key in your iQ Block Country settings your license key will be validated at our API service and a the nearest API server to you will be chosen. To do this your website will contact all API servers once to request 
an empty file.
Once you use the API service the IP address of your visitors and your API key are send to one of the API servers and converted to a country. The plugin checks if the visitor should be blocked based on that country or not.
What is logged on our end? 
* Upon validation of your license key your request will be logged in our webserver logs. (This will be the IP address of your webserver). 
* Upon checking an IP address of your visitor this IP address is only used to convert it to the country it belongs to and is not logged. We have no way to link a visitors IP address to your website. 
 What is logged is your API Key and the Website URL making the request.
If you decide to purchase the GeoIP API key your chosen payment account will be charged by on a time basis. This subscription will not renew itself unless you subscribed to our service prior to September 2024.
Privacy policy regarding this service specific can be found here: https://webence.nl/wp-content/uploads/2022/06/Privacy-Policy-Webence-API.pdf
<h3>MaxMind Database Usage</h3>
This plugin uses the Free version of the MaxMind GeoIP2 Country Database. You can also use the paid version but will have to make sure it is uploaded to the same location with the filename of Free database.
MaxMind Terms of Use: https://www.maxmind.com/en/terms-of-use 
MaxMind Privacy Policy: https://www.maxmind.com/en/privacy-policy

iQ Block Country


I've used this on more than a dozen sites over the years, and the functionality has been fantastic. I do wish there was an easier way to keep the IPs current without FTP, but I'm a fan. Keep up the good work!


Multiple Sites - No Issues For Years

Allow or disallow visitors from certain countries accessing (parts of) your website

Comment Timeout vs iQ Block Country