Feature #28474

Check if output of extensions has changed

Added by Simon Schaufelberger almost 10 years ago. Updated about 1 year ago.

Must have
Indexed Search
Target version:
Start date:
Due date:
% Done:


Estimated time:
PHP Version:
Sprint Focus:


At the moment indexed search checks only the last modification timestamp of the page itself and the content elements but does NOT know about the output of the plugins. I have a extension that renders a cached list of database entries. whenever someone adds an item to the list, the cache is emptied and the page is reloaded, the new output is there BUT indexed_search does NOT know about this change.

Something should be done to let indexes_seach know that the content has changed, otherwise the new content only gets indexed when the page properties or a content element changes.


Updated by Oliver Hader about 8 years ago

  • Target version set to 2222

Updated by Oliver Hader about 8 years ago

  • Project changed from 1382 to TYPO3 Core

Updated by Oliver Hader about 8 years ago

  • Category set to Indexed Search

Updated by Oliver Hader about 8 years ago

  • Target version deleted (2222)

Updated by Mathias Schreiber over 6 years ago

  • Target version set to 7.5

Updated by Benni Mack over 5 years ago

  • Target version changed from 7.5 to 7 LTS

Updated by Tymoteusz Motylewski about 5 years ago

and can't you trigger a cache clearing for the page once your record is modified?


Updated by Simon Schaufelberger about 5 years ago

yes, that would be a workaround but there should be a general approach since it it also affects third party extensions which i don't want to patch.


Updated by Benni Mack about 1 year ago

  • Status changed from New to Closed

So you're saying the index should get removed (or put on the reindexing list) when a page was modified or one of (cacheable) plugins has a different output?

Removing an index entry would be a bad UX approach IMHO, but maybe configurable. Currently however it is not possible to find out which index cache entries should be flushed, as TYPO3 does not (exclusively) work with cache tags. That would be one solution to trigger this, but will be handled separately (as indexed search is just one part of that issue)

Also available in: Atom PDF