You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use mksearch with Elasticsearch which works well. But i found that deleted pages don't get removed from the index when the page has a content element (which normally is always the case).
I have verified this error with a fresh TYPO3 9.5.23 installation and version 9.5.16 of dmk/mksearch, both installed via Composer. Steps to reproduce:
I made a page named "A" and a page named "B". Page B has a text/image content element with just a header and a sentence.
I created a mksearch index for Elasticsearch ("test;localhost,9200,;").
Add a indexer config type core : page. Only edited config here is "include.pageTrees.0 = 1".
Index the queue and check that both pages are in the Elasticsearch index. I used Kibana for that.
Delete pages A and B. Reindex the queue again.
Result: In Kibana i still see page B, page A has been removed from the index.
Expected: both pages should have been removed from the index.
The text was updated successfully, but these errors were encountered:
We need to check this problem. But this should have nothing to do with the content element as the page indexer doesn't mind the content elements on it at all.
Btw, if you want the content of a page to be indexed and searched you need to use the indexer core.tt_content. This indexer should take care of deleted pages on top. Maybe this solves your problem after all.
Thanks for your response and the hint with the content indexer @hannesbochmann .
In the project where i stumbled over the page deletion bug we removed the content indexer which we had added at the beginning. We had to many very small content Elements which just bloated the search index. So the search results weren't useful in a lot of cases. We removed the tt_content indexer and extended the page indexer to also index the text of the content elements of the pages. That made the search results more accurate because every page had just one instance in the index and it's content could be analyzed better by Elasticsearch.
I use mksearch with Elasticsearch which works well. But i found that deleted pages don't get removed from the index when the page has a content element (which normally is always the case).
I have verified this error with a fresh TYPO3 9.5.23 installation and version 9.5.16 of dmk/mksearch, both installed via Composer. Steps to reproduce:
Result: In Kibana i still see page B, page A has been removed from the index.
Expected: both pages should have been removed from the index.
The text was updated successfully, but these errors were encountered: