Project

General

Profile

Actions

Bug #93031

closed

Page is not being reindexed by EXT:indexed_search

Added by Sven Burkert over 3 years ago. Updated about 1 month ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Indexed Search
Target version:
-
Start date:
2020-12-08
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
10
PHP Version:
7.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

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".

Actions #1

Updated by Tomas Norre Mikkelsen almost 2 years ago

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-->
)    
Actions #2

Updated by Sven Burkert over 1 year ago

@Tomas Norre Mikkelsen 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).

Actions #3

Updated by Sybille Peters about 1 year ago

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

Actions #4

Updated by Sven Burkert about 1 year ago

@Sybille Peters Yes, I've checked the same test scenario in v11

Actions #5

Updated by Christian Kuhn about 1 month ago

  • Status changed from New to Closed

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.

Actions

Also available in: Atom PDF