Access Blocker (a pseudo-recaptcha)
|
This drop-in plugin provides your store with admin-level controls to block (or limit) actions provided by the contact_us, create_account and login pages. If access is blocked via admin-level configuration: 1. contact_us. The message appears to be sent, but no email is actually generated. 2. create_account. An account appears to have been created, but it's not (and no emails are sent). The message (defined in the plugin's message-file) is displayed to give the illusion of an account having been created. 3. login. The login is denied, with the "standard" Error: Sorry, there is no match for that email address and/or password. message being displayed. It is more than an IP Blocker. Some features of the plugin require that you request a free API key from the ipdata.co (https://ipdata.co) service. That service identifies "known" threats, based on a supplied IP address — Access Blocker makes that request based on the IP address used to access your site. |
 Zen Cart® Versions |
v1.5.5, v1.5.6, v1.5.7, v1.5.8, v2.0.0 |
 Original Author |
lat9 |
| Last Updated by |
lat9 - 16 Jun 2024 |
 Downloads |
802 |
Version History
| Access Blocker (a pseudo-recaptcha) - Version: v1.5.2 | |||||||||||||
|
This release contains corrections associated with the following GitHub issues: #19: Don't send ipdata.co requests for internal IP addresses. #20: Add commentary to blocked_accesses.php, identifying its purpose and how to use. #21: Don't block cron-jobs when Totally restrict access on threats is active. #22: Enable whitelisted IP addresses to regain access after having been found to be a threat. |
|||||||||||||
|
|||||||||||||
| Access Blocker (a pseudo-recaptcha) - Version: v1.5.1 | |||||||||||||
|
This release contains changes associated with the following GitHub issues: #15: Ensure that all class properties are predefined, required for PHP 8.2. #16: Account for "rolling" session IP addresses. #17: organization property no longer returned, now in company->name and/or asn->name. |
|||||||||||||
|
|||||||||||||
| Access Blocker (a pseudo-recaptcha) - Version: v1.5.0 | |||||||||||||
|
This release contains changes associated with the following GitHub issues: #12: Added a configuration setting to enable the use of the EU-based endpoint. #13: Added a configuration setting to force accesses after a threat was detected to an HTTP 410 (Gone) response. #14: Use zen_cfg_read_only as the setting function for the plugin's version. |
|||||||||||||
|
|||||||||||||
| Access Blocker (a pseudo-recaptcha) - Version: v1.4.0 | |||||||||||||
| This version adds settings for an IP-address and an email-address whitelist, enabling a site to 'unblock' a customer whose Internet provider has been recorded as a threat by ipdata.co. | |||||||||||||
|
|||||||||||||
| Access Blocker (a pseudo-recaptcha) - Version: v1.3.0 | |||||||||||||
| Adding the zc157+ version of ask_a_question to the list of pages protected; see GitHub issue #10 for additional information. | |||||||||||||
|
|||||||||||||
| Access Blocker (a pseudo-recaptcha) - Version: v1.2.0 | |||||||||||||
|
This release provides an integration with the One-Page Checkout, disabling its Guest Checkout mode if a blocked IP is in effect. See GitHub issue #9 for additional information. Note: Supported on an unsuffixed zc157 ONLY IF all currently documented bugfixes have been applied. |
|||||||||||||
|
|||||||||||||
| Access Blocker (a pseudo-recaptcha) - Version: v1.1.1 | |||||||||||||
| This release corrects the generation of PHP notices when one or more of the submitted form-fields is missing; see GitHub issue #8. | |||||||||||||
|
|||||||||||||
| Access Blocker (a pseudo-recaptcha) - Version: v1.1.0 | |||||||||||||
|
This release contains changes associated with the following GitHub issues: #6: Don't require ipdata.co access if otherwise blocked #7: Add blocking by company name during the create-account process |
|||||||||||||
|
|||||||||||||
| Access Blocker (a pseudo-recaptcha) - Version: v1.0.1 | |||||||||||||
|
This release contains changes associated with the following GitHub issues: #1: Added missing license. #3: Correct log, indicating the IP address that was denied. #4: For site performance, only request the ipData information on pages being filtered. #5: Modify configuration settings to use a textarea box (allows admins to see what's been previously entered). |
|||||||||||||
|
|||||||||||||
| Access Blocker (a pseudo-recaptcha) - Version: 1.0.0 | |||||||||||||
|
This drop-in plugin provides your store with admin-level controls to block (or limit) actions provided by the contact_us, create_account and login pages. If access is blocked via admin-level configuration: 1. contact_us. The message appears to be sent, but no email is actually generated. 2. create_account. An account appears to have been created, but it's not (and no emails are sent). The message (defined in the plugin's message-file) is displayed to give the illusion of an account having been created. 3. login. The login is denied, with the "standard" Error: Sorry, there is no match for that email address and/or password. message being displayed. Some features of the plugin require that you request a free API key from the ipdata.co (https://ipdata.co) service. That service identifies "known" threats, based on a supplied IP address — Access Blocker makes that request based on the IP address used to access your site. |
|||||||||||||
|
|||||||||||||
Date Added
File Size
Encapsulated?
