You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
trying to create a new Scheduler Task "Event Queue Worker" throws a TypeError Exception
ApacheSolrForTypo3\Solr\Task\EventQueueWorkerTask::setLimit(): Argument #1 ($limit) must be of type int, null given, called in /var/www/html/vendor/apache-solr-for-typo3/solr/Classes/Task/EventQueueWorkerTaskAdditionalFieldProvider.php on line 102
if you set your exceptionalErrors to include Warnings you got a TYPO3\CMS\Core\Error\Exception
PHP Warning: Undefined array key "solr_eventqueueworkertask_limit" in /var/www/html/vendor/apache-solr-for-typo3/solr/Classes/Task/EventQueueWorkerTaskAdditionalFieldProvider.php line 102
To Reproduce
Steps to reproduce the behavior:
Go to Scheduler Module
Click on new Task
Select Event Queue Worker
Choose proper Frequency
save
Expected behavior
Task is saved
Screenshots
Used versions (please complete the following information):
TYPO3 Version: 12.4.5
EXT:solr Version: 12.0.0-beta-1
PHP 8.1
The text was updated successfully, but these errors were encountered:
Describe the bug
trying to create a new Scheduler Task "Event Queue Worker" throws a TypeError Exception
ApacheSolrForTypo3\Solr\Task\EventQueueWorkerTask::setLimit(): Argument #1 ($limit) must be of type int, null given, called in /var/www/html/vendor/apache-solr-for-typo3/solr/Classes/Task/EventQueueWorkerTaskAdditionalFieldProvider.php on line 102
if you set your exceptionalErrors to include Warnings you got a TYPO3\CMS\Core\Error\Exception
PHP Warning: Undefined array key "solr_eventqueueworkertask_limit" in /var/www/html/vendor/apache-solr-for-typo3/solr/Classes/Task/EventQueueWorkerTaskAdditionalFieldProvider.php line 102
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Task is saved
Screenshots
Used versions (please complete the following information):
The text was updated successfully, but these errors were encountered: