[SOLVED] Error in showing the search results of indexed search

TYPO3 Questions
1

Hi, I updated my system to

Typo3 13.4.15
bootstrap_package 15.0.3
introduction package 4.7.0
“classic” installation

Server is
debian 12
PHP 8.4.11

The years before I used ke_search but now I want to switch back to indexed_search.

The extension is active.
The pages get indexed.
I made the site set etc.and I inserted an Indexed Search Form on a page.

Instead of search results I get “Oops, an error occurred! Request: …”

The log shows

*`Mon, 18 Aug 2025 14:19:01 +0200 [ALERT] request="594b03ef88aeb" component="TYPO3.CMS.Frontend.ContentObject.Exception.ProductionExceptionHandler": Oops, an error occurred! Request: 594b03ef88aeb- Exception: Fluid parse error in template Search_action_search_db4e780aeb4e68d6, line 30 at character 22. Error: The ViewHelper "<is:pageBrowsingResults>" could not be resolved.`*

Seemed to be the problem like this

But in the actual version this should be solved, as I saw in the affected file.

I think it’s no cache-problem. And I even tested on different browsers and a similar installation.

Nevertheless I can’t find a solution.
Is there some configuration missing?

I would be grateful for any help
Thanks
Klaus

2

Do you use your own template for the indexed_search? The view helper <is:pageBrowsingResults> does not exist anymore. It was removed from v12 to v13.

You need to update your custom template and merge your changes with the changes made to v13.

3

Hi Thomas,

thank you very much for your reply.

I’ve got no own package for indexed_search.

Once again I checked the file Search.html in bootstrap_package 15.0.3.

I might be wrong but pageBrowsing and pageBrowsingResults are still used there. Changing this according to [BUGFIX] Adapt use of removed ViewHelper in EXT:indexed_search by garvinhicking · Pull Request #1537 · benjaminkott/bootstrap_package · GitHub the search results ars shown.

Nevertheless do I get the correct number of search results but can only see 1-10. The links to 11-20, 21-30 etc. do not work… We will see.

Thank you so far!

Klaus

4

Hi,

referring to my last post I unfortunately have to report that the shown number of search results is not correct.

I solved the problem of not working links for results higher then 10.

But it is some mysterious:

The search gives the number of 37 results - showing 1-10.
Going to 11-20 the number of results changes to 26.
Going to 21-30 the number of results changes to 23 - this should be the correct number.

Using the extended seach with 10 results at the same time gives the same behaviour.
Using the extended search with 25 (or more) results the correct 23 are shown.

One more time I’m asking for help or a hint.

Does anybody know about this strange behaviour?

Thanks a lot

Klaus

5

Hi Klaus, that’s a performance optimization that you can disable: TypoScript — Indexed Search main documentation

6

Hi Jonas,

thank you very much - that works!

Best wishes

Klaus

7

I always have the same problem with Typo 13.4.21 and

bootstrap_package 15.0.4

and your demo site has the same problem

https://www.bootstrap-package.com/content-examples/form-elements/search?tx_indexedsearch_pi2\[action\]=search&tx_indexedsearch_pi2\[controller\]=Search&cHash=31137d1d217c346e53cf51d3a34b6f90 TYPO3 ships with a ready to use search. Oops, an error occurred! Request: 3beb5c2003d72
8

Whenever there is an “oops” error, you can find more information about it in the log file.

It is usually found at ./var/log/typo3_….log

9

The demo site bootstrap.com has the same problem

on my site Oops, an error occurred! Request: 585c130950403

Tue, 09 Dec 2025 16:53:12 +0100 [ALERT] request=“585c130950403” component=“TYPO3.CMS.Frontend.ContentObject.Exception.ProductionExceptionHandler”: Oops, an error occurred! Request: 585c130950403- Exception: Fluid parse error in template Search_action_search_ef80c75729af4730, line 30 at character 22. Error: The ViewHelper “is:pageBrowsingResults” could not be resolved.
Based on your spelling, the system would load the class “TYPO3\CMS\IndexedSearch\ViewHelpers\PageBrowsingResultsViewHelper”, however this class does not exist. (error code 1407060572). Template source chunk: <is:pageBrowsingResults numberOfResults=“{result.count}” currentPage=“{searchParams.pointer}” resultsPerPage=“{searchParams.numberOfResults}” />, in file /srv/www/htdocs/sgc/vendor/typo3fluid/fluid/src/Core/Parser/TemplateParser.php:131 - {“exception”:"TYPO3Fluid\Fluid\Core\ViewHelper\UnresolvableViewHelperException: Based on your spelling, the system would load the class “TYPO3\CMS\IndexedSearch\ViewHelpers\PageBrowsingResultsViewHelper”, however this class does not exist. in /srv/www/htdocs/sgc/vendor/typo3fluid/fluid/src/Core/ViewHelper/ViewHelperCollection.php:32\nStack trace:\n#0 /srv/www/htdocs/sgc/vendor/typo3fluid/fluid/src/Core/ViewHelper/ViewHelperResolver.php(549): TYPO3Fluid\Fluid\Core\ViewHelper\ViewHelperCollection->resolveViewHelperClassName()\n#1 /srv/www/htdocs/sgc/vendor/typo3fluid/fluid/src/Core/ViewHelper/ViewHelperResolver.php(425): TYPO3Fluid\Fluid\Core\ViewHelper\ViewHelperResolver->resolveViewHelperName()\n#2 /srv/www/htdocs/sgc/vendor/typo3fluid/fluid/src/Core/Parser/SyntaxTree/ViewHelperNode.php(55): TYPO3Fluid\Fluid\Core\ViewHelper\ViewHelperResolver->resolveViewHelperClassName()\n#3 /srv/www/htdocs/sgc/vendor/typo3fluid/fluid/src/Core/Parser/TemplateParser.php(353): TYPO3Fluid\Fluid\Core\Parser\SyntaxTree\ViewHelperNode->__construct()\n#4 /srv/www/htdocs/sgc/vendor/typo3fluid/fluid/src/Core/Parser/TemplateParser.php(305): TYPO3Fluid\Fluid\Core\Parser\TemplateParser->initializeViewHelperAndAddItToStack()\n#5 /srv/www/htdocs/sgc/vendor/typo3fluid/fluid/src/Core/Parser/TemplateParser.php(238): TYPO3Fluid\Fluid\Core\Parser\TemplateParser->openingViewHelperTagHandler()\n#6 /srv/www/htdocs/sgc/vendor/typo3fluid/fluid/src/Core/Parser/TemplateParser.php(116): TYPO3Fluid\Fluid\Core\Parser\TemplateParser->buildObjectTree()\n#7 /srv/www/htdocs/sgc/vendor/typo3fluid/fluid/src/Core/Parser/TemplateParser.php(174): TYPO3Fluid\Fluid\Core\Parser\TemplateParser->parse()\n#8 /srv/www/htdocs/sgc/vendor/typo3fluid/fluid/src/Core/Parser/TemplateParser.php(160): TYPO3Fluid\Fluid\Core\Parser\TemplateParser->parseTemplateSource()\n#9 /srv/www/htdocs/sgc/vendor/typo3fluid/fluid/src/View/AbstractTemplateView.php(383): TYPO3Fluid\Fluid\Core\Parser\TemplateParser->getOrParseAndStoreTemplate()\n#10 /srv/www/htdocs/sgc/vendor/typo3fluid/fluid/src/View/AbstractTemplateView.php(141): TYPO3Fluid\Fluid\View\AbstractTemplateView->getCurrentParsedTemplate()\n#11 /srv/www/htdocs/sgc/vendor/typo3/cms-fluid/Classes/View/FluidViewAdapter.php(57): TYPO3Fluid\Fluid\View\AbstractTemplateView->render()\n#12 /srv/www/htdocs/sgc/vendor/typo3/cms-extbase/Classes/Mvc/Controller/ActionController.php(897): TYPO3\CMS\Fluid\View\FluidViewAdapter->render()\n#13 /srv/www/htdocs/sgc/vendor/typo3/cms-indexed-search/Classes/Controller/SearchController.php(226): TYPO3\CMS\Extbase\Mvc\Controller\ActionController->htmlResponse()\n#14 /srv/www/htdocs/sgc/vendor/typo3/cms-extbase/Classes/Mvc/Controller/ActionController.php(470): TYPO3\CMS\IndexedSearch\Controller\SearchController->searchAction()\n#15 /srv/www/htdocs/sgc/vendor/typo3/cms-extbase/Classes/Mvc/Controller/ActionController.php(390): TYPO3\CMS\Extbase\Mvc\Controller\ActionController->callActionMethod()\n#16 /srv/www/htdocs/sgc/vendor/typo3/cms-extbase/Classes/Mvc/Dispatcher.php(68): TYPO3\CMS\Extbase\Mvc\Controller\ActionController->processRequest()\n#17 /srv/www/htdocs/sgc/vendor/typo3/cms-extbase/Classes/Core/Bootstrap.php(152): TYPO3\CMS\Extbase\Mvc\Dispatcher->dispatch()\n#18 /srv/www/htdocs/sgc/vendor/typo3/cms-extbase/Classes/Core/Bootstrap.php(131): TYPO3\CMS\Extbase\Core\Bootstrap->handleFrontendRequest()\n#19 /srv/www/htdocs/sgc/vendor/typo3/cms-frontend/Classes/ContentObject/ContentObjectRenderer.php(4512): TYPO3\CMS\Extbase\Core\Bootstrap->run()\n#20 /srv/www/htdocs/sgc/vendor/typo3/cms-

10

This means that the overwritten template Search/Search.html (bootstrap_package/Resources/Private/Templates/IndexedSearch/Search/Search.html at master · benjaminkott/bootstrap_package · GitHub) uses a TYPO3 Viewhelper that is not valid any more. The original of that file is a template of the (Core-) Extension typo3/cms-indexed-search.

To start afresh, it is advisable to not overwrite these templates.

The bootstrap-package is not an official TYPO3 extension. I don’t know it well, but it seems it is not compatible with the version of typo3/cms-indexed-search (which is linked to the Core version) you are using. You can add an issue here: GitHub · Where software is built