Bug #88493
closedException in Indexed Search Administration Modul
0%
Description
TYPO3 v9.5.7
If I switch in the Backend Modul "Indexing" to "List: Pages" the attached error appears. All other possible selections are working fine.
(1/1) #1476107295 TYPO3\CMS\Core\Error\Exception
PHP Warning: json_decode() expects parameter 1 to be string, array given in /is/xxxxxxxxxxxxxxxxx/www/typo3_src-9.5.7/typo3/sysext/indexed_search/Classes/Domain/Repository/AdministrationRepository.php line 363
Installed EXT: Bootstrap Package, News, dpn_glossary
Files
Updated by Georg Ringer over 5 years ago
- Status changed from New to Needs Feedback
Can you remove this index entry from the table index_phash
(or truncate all indexed_search tables) and check if this occours? I see no way how this can happen currently
Updated by Andrea Moroni over 5 years ago
After truncating all indexed_search tables and a re-index the error keeps occuring
Core: Error handler (BE): PHP Warning: json_decode() expects parameter 1 to be string, array given in /is/xxxxxxxx/typo3_src-9.5.7/typo3/sysext/indexed_search/Classes/Domain/Repository/AdministrationRepository.php line 363
Could it be a problem with hosteurope PHP 7.2.18-he.0 ?
Updated by Boris Schauer over 5 years ago
I have the same issue on another Hoster
Updated by Tobias Gülzow over 5 years ago
Georg Ringer wrote:
Can you remove this index entry from the table
index_phash
(or truncate all indexed_search tables) and check if this occours? I see no way how this can happen currently
Hi Georg.
The method addAdditionalInformation() already decoded the json, hence the array in the error message.
@see
https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/indexed_search/Classes/Domain/Repository/AdministrationRepository.php#L359
and
https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/indexed_search/Classes/Domain/Repository/AdministrationRepository.php#L449
Tobi
Updated by Tilo Baller about 5 years ago
- Related to Bug #89081: PHP Warning in Backend Module Indexing -> List: Pages added
Updated by Oliver Hader about 5 years ago
- Status changed from Needs Feedback to Resolved
- Target version set to next-patchlevel
Resolved with #89081