Issue Bug Closed

#93031Page is not being reindexed by EXT:indexed_search

Sven Burkert 12/08/20, 18:48 updated 04/06/24, 11:07

Description

I have the problem that my website content isn’t reindexed, the index record contains the old page contents.

I’ve broken it down to a simple site setup with this TypoScript setup:

page = PAGE
page.10 = TEXT
page.10.value = aaa1
config.index_enable = 1

When I open this page in frontend, the text “aaa1” is displayed and the page is indexed by EXT:indexed_search (a new index record is created and displayed in module “Indexing -> Detailed statistics”).
Now I slightly change this TypoScript (page.10.value = aaa1 aaa2) and open the page again in frontend. The record in “Indexing -> Detailed statistics” is updated (it shows the current timestamp in column “Indexed”), but when clicking on this record for detailed statistics, the row “item_description” still shows “aaa1”.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

History 5

  1. Tomas Norre Mikkelsen commented 06/17/22, 06:48

    Have you perhaps forgotten the markers in the template?

    <!--TYPO3SEARCH_begin-->
    <!--TYPO3SEARCH_end-->

    https://docs.typo3.org/c/typo3/cms-indexed-search/main/en-us/TechnicalDetails/HtmlContent/Index.html#html-content

    This simple example works for me: I’m on 12.0.0 though. But should be the same.

    page = PAGE
    page.config.index_enable = 1
    
    page.10 = TEXT
    page.10.value (
       <!--TYPO3SEARCH_begin-->
    )
    
    page.100 = CONTENT
    page.100 {
        table = tt_content
        select {
            orderBy = sorting
            where = {#colPos}=0
        }
    }
    
    page.1000 = TEXT
    page.1000.value (
       <!--TYPO3SEARCH_end-->
    )    
  2. Sven Burkert commented 12/14/22, 09:01

    @tomasnorre No, I didn’t add the markers, because these are optional. But I’ve checked it in TYPO3 v11 (without markers), worked as expected (text was found via search).

  3. Sybille Peters commented 03/06/23, 19:02

    So you are saying, the problem appears in v10, but not in v11 with the same test scenario?

  4. Sven Burkert commented 03/07/23, 11:49

    @speters Yes, I’ve checked the same test scenario in v11

  5. Christian Kuhn commented and changed status New Closed 04/06/24, 11:07

    Hey.

    I hope it’s ok to close here: v10 is out of support and the issue reporter states the issue does not occur in v11.