Bug #81986
closedindexed_search generates duplicated results for same page
0%
Description
Hi community.
The issue is quite weird and it is a combination of multiple factors. Let's go step by step.
Website menu links are generated via <f:link.page pageUid="{mainMenuItem.uid}">{mainMenuItem.linktext}</f:link.page>
and since f.link.page
by default uses cHash, the links look like http://domain.tld/index.php?id=11&L=0&cHash=82665c06c7bb6aebebc536bd4da96382
Not critical and with RealURL the path still looks nice, e.g. domain.tld/about-us/
But if somewhere else a link to a same page is generated without cHash, the page is duplicated in index:
And then if I search for some words, that are available on such a page it might appear twice:
First like a normal links with cHash:
http://domain.tld/index.php?id=11&L=0&cHash=82665c06c7bb6aebebc536bd4da96382
And second time as the same link but with duplicated id
:
http://domain.tld/index.php?id=11&L=0&id=11&cHash=82665c06c7bb6aebebc536bd4da96382
The main problem is, that I can't reproduce duplicated search results in my development environment (although duplicated indexing results and result link with double-id are still reproducible), but it is a case on a production server.
As a poor-man's fix, one can force noCacheHash
for page links, but it seems ugly and still no guarantee, that link with cHash can be generated in some other part of the website.
The main question here: is it broken indexing, which indexes same page twice or is search, which duplicates the 'id' parameter? Or both?
TYPO3 8.7.3
Files
Updated by Mona Muzaffar over 7 years ago
- Related to Bug #30852: Multilingual search in translated pages: Results of default language always linking to current language added
Updated by Mona Muzaffar over 7 years ago
- Related to Bug #81164: Indexed Search appends ?L=0 to URLs of search results added
Updated by Riccardo De Contardi about 5 years ago
Is this issue still reproducible on version 9 ?
Updated by David Bruchmann over 4 years ago
The behavior is still reproduce-able even in version 10.4.1 if the indexing configuration is not setup correctly.
As example for a correct setup I list my configuration for tx_news:
Fieldlist:
title,teaser,bodytext
GET-Parameter:
&tx_news_pi1[news]=[_TABLE:tx_news_domain_model_news;_PID:{$plugin.tx_news.settings.startingpoint}]
Important is that the record of indexing configuration has to be enabled in the access-tab, without that the wrong behavior might be reproduce-able.
Updated by Riccardo De Contardi 6 months ago
- Status changed from New to Needs Feedback
URL/Link generation and usage of indexable context has come a long way since TYPO3 v8 or the last update of this ticket with v10.
It would help a lot if you could check out if this still applies to an indexed search setup, and what kind of site / routing configuration you are using
Thank you and sorry for this so late reply.
Updated by Benni Mack 2 months ago
- Status changed from Needs Feedback to Closed
We had to fix this via a breaking change in TYPO3 v13.0. Due to lack of feedback, I take the liberty of closing the issue - if you feel this is the wrong decision, let me know!