Project

General

Profile

Actions

Bug #80730

closed

EXT:indexed_search FLUID based does not indexes new created pages with 8.7.0

Added by Angelo Previtali about 7 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Indexed Search
Target version:
-
Start date:
2017-04-06
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
8
PHP Version:
7.0
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

After Upgrading from 8.6.1 to the latest 8.7.0 the EXT:indexed_search does not indexes new created pages. Even if we deleted the whole index in BE to Reindexing it from the FE after loading the page.

Actions #1

Updated by rainer karnowski about 7 years ago

the same here ... worked with typo3 v8.6.1 but not anymore in v 8.7.0

Actions #2

Updated by Angelo Previtali about 7 years ago

We just checked on thing: With a brandnew installation of the V8.7.0 normal pages gets indexed correctly.

Actions #3

Updated by Michel Rossier about 7 years ago

  • PHP Version changed from 7.1 to 7.0

Exact same issues on any of my updated systems (8.6.1 to 8.7):
- search does work as long as there are entries in the index
- but no more new pages are indexed after the upgrade
- as soon as the index is flushed, it stays empty and no more pages or news articles get indexed.

I tried to reinstall the extension, renewed the encryption key, deleted caches, but nothing is of help so far.

There are no problems when installing an 8.7 from scratch on the same hosting.

Actions #4

Updated by Angelo Previtali about 7 years ago

  • % Done changed from 0 to 100

Problem resolved: By disabling those "old" TS in Setup from older TYPO3 configurations the indexed_search works fine again.

config {
no_cache = 1
cache = 0
}

Actions #5

Updated by Riccardo De Contardi about 7 years ago

  • Status changed from New to Closed
  • Target version deleted (next-patchlevel)

I close this one as resolved, then. Thank you for your answer and findings.

If you think that this is the wrong decision or experience the issue again, then please reopen it or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF