Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt November 11, 2024
PanSevence Posted May 16, 2024 Posted May 16, 2024 I am experiencing an issue with starting the task after updating to 4.7.17 beta 2. Are you experiencing similar problems? ValueError: max(): Argument #1 ($value) must contain at least one element (0) #0 applications/core/tasks/unlockmembers.php(53): max() #1 system/Task/Task.php(281): IPS\core\tasks\_unlockmembers->execute() #2 applications/core/modules/admin/settings/advanced.php(751): IPS\_Task->run() #3 system/Dispatcher/Controller.php(107): IPS\core\modules\admin\settings\_advanced->runTask() #4 applications/core/modules/admin/settings/advanced.php(38): IPS\Dispatcher\_Controller->execute() #5 system/Dispatcher/Dispatcher.php(153): IPS\core\modules\admin\settings\_advanced->execute() #6 admin/index.php(13): IPS\_Dispatcher->run() #7 {main} #0 init.php(1036): IPS\_Log::log() #1 [internal function]: IPS\IPS::exceptionHandler() #2 {main}
Marc Posted May 16, 2024 Posted May 16, 2024 So you have any 3rd party items running when you are testing this?
Nathan Explosion Posted May 16, 2024 Posted May 16, 2024 48 minutes ago, Marc Stridgen said: So you have any 3rd party items running when you are testing this? It's easy to reproduce - just lock an account out, then go to the ACP and manually run the task.
Marc Posted May 16, 2024 Posted May 16, 2024 Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.
PanSevence Posted May 23, 2024 Author Posted May 23, 2024 After updating to 4.7.17 beta 3, the problem disappeared and I was able to manually run the cron job without any issues. Daniel F 1
Recommended Posts