[BUG] Wrong is_rootpage for translated rootpages

[naturefund-falk]

At first: this is mostly an configuration issue, but very hard to debug. If you have a wrong value of 0 in the is_rootpage field of the translated rootpage, it causes some errors in the plugin. These errors are, that the indexer throws an error on translated pages and you cannot open the search page (‘Search is currently not available.').

Steps to reproduce the behavior: Change the is_rootpage field of a translated rootpage to 0. I think this was an upgrading issue.

Expected behavior Because there are no other typo3 errors caused by this, i would expect this is also not causing a problem in EXT:solr

Used versions (please complete the following information):

• TYPO3 Version: 10.4.31
• EXT:solr Version: 11.2.0
• Used Apache Solr Version: the docker release-11.2.x container

Additional context Im not sure if this needs a fix, maybe i am the only person this bug ever happened. I think this could be fixed by changing the getRootPageId in ApacheSolrForTypo3\Solr\System\Page\Rootline to use the last array entry as rootpage, even if Site::isRootPage failed.

[dmitryd]

This is not really a bug of solr. If your data is incorrect, why would it be a problem of solr?

Think of your house. If you have a wrong key to the entrance door, is it the problem of the lock maker? Probably not...