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
Fetching nested TypoScript setup via ApacheSolrForTypo3\Solr\FrontendEnvironment\TypoScript::ext_getSetup(array $theSetup, string $theKey) results the following warning during indexing via backend:
Reading nested TypoScript will no longer log a warning when the
value can not be accessed. In this case, the second value in the
array returned in `TypoScript::ext_getSetup` will be an empty string.
However, the second value is not used by Ext:solr anymore.
This also fixes an issue with PHP 8 where such warning would cause the
indexing to fail, when the method is used inside of an indexer.
Fixes: #3359
Reading nested TypoScript will no longer log a warning when the
value can not be accessed. In this case, the second value in the
array returned in `TypoScript::ext_getSetup` will be an empty string.
However, the second value is not used by Ext:solr anymore.
This also fixes an issue with PHP 8 where such warning would cause the
indexing to fail, when the method is used inside of an indexer.
Fixes: #3359
Ports: #3360
Describe the bug
Fetching nested TypoScript setup via
ApacheSolrForTypo3\Solr\FrontendEnvironment\TypoScript::ext_getSetup(array $theSetup, string $theKey)
results the following warning during indexing via backend:This warning then results in an error during indexing.
To Reproduce
TypoScript setup:
Snipped, placed inside a Solr indexer or Solr indexer hook:
Expected behavior
Missing value assignments to TypoScript structures should be ignored, defaulting to an empty string
as the original method of TYPO3 v11 does:
https://github.com/TYPO3/typo3/blob/11.5/typo3/sysext/core/Classes/TypoScript/ExtendedTemplateService.php#L304
Used versions (please complete the following information):
The text was updated successfully, but these errors were encountered: