TYPO3 Core

I can only copypaste you the entire exception :

Core: Exception handler (WEB): Uncaught TYPO3 Exception: An exception occurred while executing 'SELECT "uid" FROM "pages" WHERE ("pid" = ?) AND ("sys_language_uid" = 0) AND (1 AND ("pages"."hidden" = 0) AND ("pages"."starttime" <= 1701096660) AND (("pages"."endtime" = 0) OR ("pages"."endtime" > 1701096660))) AND ("pages"."deleted" = 0) ORDER BY "uid" ASC' with params [5645]: SQLSTATE⁴²⁸⁰⁴: Datatype mismatch: 7 ERROR: argument AND must be type boolean, and not type integer LINE 1: ...RE ("pid" = $1) AND ("sys_language_uid" = 0) AND (1 AND ("p... ^ | Doctrine\DBAL\Exception\DriverException thrown in file /var/www/html/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/AbstractPostgreSQLDriver.php in line 102. Requested URL: {mydomain}/typo3/index.php?route=%%2Frecord%%2Fcommit&token=--AnonymizedToken--&cmd[pages]⁵⁶⁴⁵[localize]=1&redirect=%%2Ftypo3%%2Findex.php%%3Froute%%3D%%252Fweb%%252Flist%%252F%%26token%%3Dc31a08c130b80c96877c5ef13fb3ed2c8719af1b%%26id%%3D5638%%26table%%3D%%26imagemode%%3D1%%26justLocalized%%3Dpages%%253A5645%%253A1

I've tried to dig into the core, like the DataHandler or the BackendConfigurationManager but I've not been able to find where the query's built.

Every translate button trigger the exception. Be it the select menu atop a page record, or a flag button in the List mode. The moment I try to translate a page, or try to copy a page, or a treelist of pages and one of them contain a "rootpage" type page, the exception is triggered.
However, translating a content doesn't seem to trigger it. It seems restrainted to pages.

Thanks. This helps.

Turns out this is a bug in ext:solr:

typo3conf/ext/solr/Classes/AbstractDataHandlerListener.php

$permissionClause = ' 1 ' . BackendUtility::BEenableFields('pages');
$treePageIdList = $queryGenerator->getTreeList($pageId, 20, 0, $permissionClause);

Class QueryGenerator then creates an 'andWhere('1 ...')' which is the postgres-invalid call.

TYPO3 v12 moved class QueryGenerator to ext:lowlevel, which is probably why current github solr now has an own getTreeList() method in ApacheSolrForTypo3\Solr\System\Records\Pages\PagesRepository. This still seems to carry the bug:

$permissionClause = ' 1 ' . $this->getPagesRepository()->getBackendEnableFields();
$treePageIdList = $this->getPagesRepository()->getTreeList($pageId, 20, 0, $permissionClause);

The ' 1 ' prefix is probably done since BackendUtility::BEenableFields('pages') adds an AND if it found something.
I guess the easiest solution is to change it to ' 1=1 ', another one is (probably) to trim() the result of BackendUtility::BEenableFields() and skip the "1", since getTreeList() will then strip the 'AND' at the beginning due to 'QueryHelper::stripLogicalOperatorPrefix($permClause)'.

-> This needs to be fixed in solr.

Could you confirm this and maybe open an issue or pull request for ext:solr maybe referencing my analysis and your backtrace?