Apache Solr for TYPO3 CMS

I currently can't reproduce your issue. By looking at the call trace I guess you ran into this issue by changing the type of page 6 from standard to sys folder at some point so that the Index Queue is a bit messed up here.

When you deleted the content element there should not have been an item in the Index Queue for page 6, and thus it should not have tried to get a site from that item. Furthermore it created a site object with page 3, which (obviously) is not a root page - also a sign that something is/went wrong in your Index Queue.

Can you try re-initializing the Index Queue through the search backend module and see if the issue remains?

Ingo Renner wrote:

I currently can't reproduce your issue. By looking at the call trace I guess you ran into this issue by changing the type of page 6 from standard to sys folder at some point so that the Index Queue is a bit messed up here.

When you deleted the content element there should not have been an item in the Index Queue for page 6, and thus it should not have tried to get a site from that item. Furthermore it created a site object with page 3, which (obviously) is not a root page - also a sign that something is/went wrong in your Index Queue.

Can you try re-initializing the Index Queue through the search backend module and see if the issue remains?

We are curently running on v.2.5.0.
I've Emptied the index, re-initialized the Index Queue, and the problem still exists. But the content outside the sysfolders that had the same problem now don't have this issue anymore. So a little progress...

Is there a special way to index sysfolders containing tt_content's?

tt_content can not be indexed (by default) as we do not index on content element level, but rather on page level. As sys folders can not be rendered you can not index content elements from those folders.

The only thing you could do is index those tt_content records as if they were tt_news (But honestly, it still doesn't sound like it makes a lot of sense to me)

• If I hide or delete a tt_content record from sysFolder [6], the exception is thrown
• There is no problem with hiding or deleting e.g. tt_news records in the same folder
• It makes no difference if the sysFolder is in- or outside of the site-root folder
• It makes no difference if [6] is a normal page or a sysFolder
• If I move [6] in the BE to another position in the page tree, I get the same exception message in nicely animated red box.

I have tried to trace the code inside the solr extension where the wrong rootPageId originates, placing devlog statements in various places from the stack trace, but - strange enough - not all code that is mentioned there appears to be run when the exception occurs, because several of these places are not logged when the exception is thrown....

I have now changed the ID sysfolder to something else, and the problem completely disappeared! I also emptied and re-build the solr index to be totally sure, but the problem seems to have gone. Nice, but completely weird???!

I have no other site to test this (except this one running on various servers, but they all act exactly identical on this), but it would be interesting to know if other sites would have a problem with hiding tt_content records from page id 6....

evil 6 ;)

can we close this issue?

Hi Ingo,
I would prefer to figure out what really caused the problem, but at the moment I'm happy that our site works again and don't have time to look further into it. You can close it now, maybe I'll give it another try later.