[TAC] Fool Bot Honey Pot 3.0.32

• logs are cleared out weekly keeping the last 3 months of logs (previously, unintentionally this was being cleared down to the last hour)

• Change to also allow the StopBotters API to be able to use ipv6 ip addresses

Change Log:

• Should be both XF1.2 and XF1.3 compatible. If XF1.3, we now make use of the core methods of storing ipv6 IP addresses:

Code:

        if (XenForo_Application::$versionId >= 1030000)
        {
            $ipAddress = XenForo_Helper_Ip::getBinaryIp();          
        }
        else
        {
            $ipAddress = $this->_getLoginModel()->convertIpToLong();
        }

• Also taken out the logging of $_SERVER, this is personal logging option that is no use to admins and also causing issues on certain servers.

• Core method to connect to API (should prevent errors being raised if API takes too long)
• Enforced passwords (call to core registration wasn't enforcing set password)

• I now run a weekly clean up to remove redundant uuids (this table was getting very large on some installs)
• The cron also deletes FBHP logs greater than 3 months old
• I now index (session_id, number)

• Fix a 1.2 issue, sometimes the registration fields are misaligned

FoolBotHoneyPot_v2_2_10b.zip
Release 17/05/2013
Change Log:

• A fix to the updater (AND addon_id = \'FoolBotHoneyPot\')

• I've noticed if all the tac plugins are installed at the same time, the API auto update for StopBotters goes wrong, this is fixed

• Fixed issue with Sex not being displayed on the registration form
• Fixed issue with form not repopulating when CAPTCHA is not correct

FoolBotHoneyPot_v2_2_07.zip

Release 26/03/2013
Change Log:

• Compatible with XF 1.1.4.
• Now calls parent actionRegister (and lets parent call the CAPTCHA unless known as bot) => Makes the PHP compatible with other plugins that use the actionRegister and should't need updating for upgraded
• Template eddit fot the Registration Form now displays the count down timer, and includes the registration Key

There is now no need to have a timer in FBHP (since XF correctly use a session timer, this is saved directly to the database and can't be manipulated... this is the same method that FBHP already used)... This timer will be removed next version
Next version, I'll use hooks for the registration page (so it will be a custom registration page based on hooks, making the registration template more compatible).

• A minor change to the actionRegister in preparation for a 1.1.4 release. This now calls the parent actionRegister, I hadn't figured out a way to do this before, since all of the POST params are changed, and the standard params are fake honey pots. Now if the user passes all FBHP checks, I reset the POST variables to what the normal registration form expects, so can now call the parent actionRegister.

=> This might mean that this plugin does not need to be updated on a 1.1.4 release