Harrison V
Member
Do you offer a install, and setup service? If so how much? Maybe you don't offer it, but are willing to? Thanks!
This plugin is amazing and 100% bulletproof. Within 2 days of getting the plugin I have 182 pages (546 bots) of blocked registrations. Simply Amazing
=> This might mean that this plugin does not need to be updated on a 1.1.4 release...
- 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.
Server Error
Invalid model 'Tac_AnyApi_Model_ApiSettings' specified
XenForo_Model::create() in XenForo/Controller.php at line 101
XenForo_Controller->getModelFromCache() in Tac/FoolBotHoneyPot/ControllerAdmin/Log.php at line 74
Tac_FoolBotHoneyPot_ControllerAdmin_Log->actionLogs() in XenForo/FrontController.php at line 310
XenForo_FrontController->dispatch() in XenForo/FrontController.php at line 132
XenForo_FrontController->run() in /store1/www/it.immobilio.www/doc_root/admin.php at line 13
After upgrading, in the fullbot log:
Code:Server Error Invalid model 'Tac_AnyApi_Model_ApiSettings' specified XenForo_Model::create() in XenForo/Controller.php at line 101 XenForo_Controller->getModelFromCache() in Tac/FoolBotHoneyPot/ControllerAdmin/Log.php at line 74 Tac_FoolBotHoneyPot_ControllerAdmin_Log->actionLogs() in XenForo/FrontController.php at line 310 XenForo_FrontController->dispatch() in XenForo/FrontController.php at line 132 XenForo_FrontController->run() in /store1/www/it.immobilio.www/doc_root/admin.php at line 13
Edit: My AnyApi version is 1.0.2
I *am* using AnyAPI 1.0.2 and FBHP 2.2.05 and have no problems. All logs normal (full of bot blocks, registrations normal)I'm not using AnyAPI, and I'm not having any issues on 2.2.05
Heh, calling the parent action kind of sucked for me because I was disabling captcha on the register page only, but now it'll require me to do more work.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.
We use essential cookies to make this site work, and optional cookies to enhance your experience.