Bug #68608
closed
Indexed search does not index all requests
0%
Description
I have on website running on 2 systems, dev and live. On the dev system indexed_search works like expected. On the live system not all pages are indexed.
The only difference is that the live system runs mysql 5.6 and the dev system mysql 5.5, php version is also different (live 5.5, dev 5.6)
Additional the live system runs in Production Context, the dev system in Development context.
Everything else is identical.
The page that is not indexed contains a cacheable plugin that shows a record of an extension i developed. The indexing is simple done via frontend rendering and the html comments. There is no crawler. I tried different approaches (cleared all index and opened the record in anonymous tab in FE, cleared all index and opened the record from preview link (with logged in backend user) and so on). Its allways the same - the dev system is capeable of indexing the record, the live system not.
The record contains special characters in the title but the table is in both systems utf8/utf8_general_ci and runs MyISAM Engine. The database is also set up with utf8 and collation utf8_general_ci. so also no difference there.
I have no idea why this happens but its annoying for my customer.
Can this be related to the mysql version? Did any of you experience the same problems?
Typo3 4 Version is 7.4-dev (89139e81a49259ec03c5ea6b0c35734f9528f5f3)
Updated by Susanne Moog over 8 years ago
- Target version changed from 7.4 (Backend) to 7.5
Updated by
Updated by Philipp Wrann over 8 years ago
Still exists, i recently changed from pibase to extbase based plugin but the behaviour is exactly the same.
Can you give me some hints how i can track down the problem?
Why is the exact same resource indexed on my localmachine - but not on the live machine?
This is very annoying for my customer.
Its not a big project, i dont want to switch to some solr search, i just want the indexed search to work.
Updated by Philipp Wrann over 8 years ago
So, i digged into the indexer a little, seems the problem is a combination of Preview-Link, Cooluri and no_cache flag.
The saved record, that is shown on the page can be previewed (save and show...), the generated link appends no_cache=1 to the url, cooluri maps that and each request is reconstituted with no_cache=1, because of that no indexing will happen and additionally performance decreases.
I dont think that is a typo3 core problem per-se but its the default behaviour of both (cooluri maps no_cache by default, typo3 adds no_cache in preview-mode by default)
So this issue is related to the cooluri extension.
Updated by Philipp Wrann over 8 years ago
It seems its a problem, that no cHash is added to the preview url, that way a wrong link is cached by the pretty url module.
Updated by Tymoteusz Motylewski over 8 years ago
- Status changed from New to Closed
Hi,
thanks for the report and sharing your findings.
I'm closing this one, as it's not TYPO3 Core related.