Project

General

Profile

Actions

Bug #105562

closed

indexed_search

Added by JAOUEN 12 days ago. Updated 12 days ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Indexed Search
Target version:
-
Start date:
2024-11-09
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
13
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Hello,
I have 2 different machines with OpenSuSE leap 15.6 and typo3 13.4.0
one is my working intranet; the other is new empty "introduction package"
on both machines the indexing is working correctly but I get "Oops, an error occurred!" as search result

1) on "introduction package" error 503

Fluid parse error in template
Search_action_search_35a2670ed8c57b6e, 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}" />

2) on my production Intranet

(1/2) #1407060572 TYPO3Fluid\Fluid\Core\Parser\Exception

Fluid parse error in template Search_action_search_7a78f47a21851a08, 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 /srv/www/htdocs/sgc/vendor/typo3fluid/fluid/src/Core/Parser/TemplateParser.php line 124

public function createParsingRelatedExceptionWithContext(\Exception $error, ?string $templateIdentifier): \Exception
{
list($line, $character, $templateCode) = $this->getCurrentParsingPointers();
$exceptionClass = get_class($error);
return new $exceptionClass(
sprintf(
'Fluid parse error in template %s, line %d at character %d. Error: %s (error code %d). Template source chunk: %s',
(string)$templateIdentifier,
$line,

at TYPO3Fluid\Fluid\Core\Parser\TemplateParser->createParsingRelatedExceptionWithContext()
in /srv/www/htdocs/sgc/vendor/typo3fluid/fluid/src/Core/Parser/TemplateParser.php line 114

$splitTemplate = $this->splitTemplateAtDynamicTags($templateString);
$parsingState = $this->buildObjectTree($splitTemplate, self::CONTEXT_OUTSIDE_VIEWHELPER_ARGUMENTS);
} catch (Exception $error) {
throw $this->createParsingRelatedExceptionWithContext($error, $templateIdentifier);
}
$this->parsedTemplates[$templateIdentifier] = $parsingState;
return $parsingState;
}

at TYPO3Fluid\Fluid\Core\Parser\TemplateParser->parse()
in /srv/www/htdocs/sgc/vendor/typo3fluid/fluid/src/Core/Parser/TemplateParser.php line 167

}
protected function parseTemplateSource(string $templateIdentifier, \Closure $templateSourceClosure): ParsingState
{
$parsedTemplate = $this->parse(
$templateSourceClosure($this, $this->renderingContext->getTemplatePaths()),
$templateIdentifier,
);
$parsedTemplate->setIdentifier($templateIdentifier);

+++ very long !

Actions #1

Updated by Garvin Hicking 12 days ago

  • Category set to Indexed Search
  • Status changed from New to Closed

Hi!

Thanks for your report.

The issue you're facing was caused by the breaking change https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/13.0/Breaking-102945-PaginationOfIndexedSearchReplaced.html in TYPO3 13. This required all IndexedSearch Templates to be changed as mentioned in the changelog.

The introduction package which uses this via the EXT:bootstrap_package must fix the issue, it is not an issue that can be adressed via the TYPO3 Core.

The issue has already been reported here:

https://github.com/FriendsOfTYPO3/introduction/issues/115

I've just created a PR for this bug: https://github.com/benjaminkott/bootstrap_package/pull/1537

Once that is adressed, and a new release of this extension and the depending introduction package is made, it would be fixed.

I'm closing the issue here and hope it helps you. You may want to create an own template using the fixed template as a sitepackage override so it does not block your progress...

Actions

Also available in: Atom PDF