2.0.0 Patch Level 3
Fixed: ErrorException: [E_WARNING] Creating default object from empty value
- ErrorException: [E_WARNING] Creating default object from empty value
- src/addons/OzzModz/SecurityLock/XF/Service/User/Login.php:43
Code:#0 src/addons/OzzModz/SecurityLock/XF/Service/User/Login.php(43): XF::handlePhpError(2, '[E_WARNING] Cre...', '/var/www/client...', 43, Array) #1 src/addons/SV/SignupAbuseBlocking/XF/Service/User/Login.php(19): OzzModz\SecurityLock\XF\Service\User\Login->validate('*****', Object(XF\Phrase)) #2 src/XF/Pub/Controller/Login.php(96): SV\SignupAbuseBlocking\XF\Service\User\Login->validate('*****', Object(XF\Phrase)) #3 src/addons/DigitalPoint/Analytics/XF/Pub/Controller/Login.php(9): XF\Pub\Controller\Login->actionLogin() #4 src/addons/OzzModz/Login/XF/Pub/Controller/Login.php(177): DigitalPoint\Analytics\XF\Pub\Controller\Login->actionLogin() #5 src/XF/Mvc/Dispatcher.php(352): OzzModz\Login\XF\Pub\Controller\Login->actionLogin(Object(XF\Mvc\ParameterBag)) #6 src/XF/Mvc/Dispatcher.php(259): XF\Mvc\Dispatcher->dispatchClass('XF:Login', 'Login', Object(XF\Mvc\RouteMatch), Object(SV\SignupAbuseBlocking\XF\Pub\Controller\Login), NULL) #7 src/XF/Mvc/Dispatcher.php(115): XF\Mvc\Dispatcher->dispatchFromMatch(Object(XF\Mvc\RouteMatch), Object(SV\SignupAbuseBlocking\XF\Pub\Controller\Login), NULL) #8 src/XF/Mvc/Dispatcher.php(57): XF\Mvc\Dispatcher->dispatchLoop(Object(XF\Mvc\RouteMatch)) #9 src/XF/App.php(2487): XF\Mvc\Dispatcher->run() #10 src/XF.php(524): XF\App->run() #11 index.php(20): XF::runApp('XF\\Pub\\App') #12 {main}
2.0.0 Patch Level 4
Fixed: Server error when a valid user tried to log in
I installed Level 2 yesterday and this error appeared this morning. Now I updated it with Level 4You got those errors before or after upgrading to 2.0.0 Patch Level 4?
Cron just seems cleaner to me, setting the security lock at the time it meets criteria. Rather than having security lock unset beyond criteria and awaiting until login to set it. No issue, just wanted to understand how it was working.Only once they attempt to login. I see no need to lock all accounts older than X.
We use essential cookies to make this site work, and optional cookies to enhance your experience.