Bug #19723
closedDefault language not always honored in result list (has patch)
0%
Description
When using indexed_search in multilanguage setups with config.linkVars containing L, there exists the following glitch:
A found result hit which has sys_language_uid=0 (ie default language) won't be linked to with the right language parameter (ie L=0) from within indexed_search's result list, if the triggering search is performed with some other than the default language (ie L>0). Instead, the result will be linked to in that other language.
The reason is, that a language parameter is only applied to a result link if the result hit has sys_language_uid > 0. This is okay and indeed desired for environments without multiple languages.
To fix this behaviour, the attached patch suggests an additional TS parameter
plugin.tx_indexedsearch.forceLanguageParamInResultList = (boolean)
that forces the L parameter in result list, even if L=0.
(issue imported from #M9983)
Files
Updated by Ralf Hettinger over 14 years ago
Hey Christopher, thanks for kicking butts (at least mine) for more Core List interaction, that's really refreshing (and I mean it) ;)
I remember that I considered this patch not clean enough for a Core/sysext suggestion - having an additional parameter for fixing a bug seems quite odd. I admit I lost track a bit on digging deeper here.
Updated by Alexander Opitz over 11 years ago
- Status changed from New to Needs Feedback
- Target version deleted (
0) - TYPO3 Version set to 4.3
The issue is very old, does this issue exists in newer versions of TYPO3 CMS (4.5 or 6.1)?
Updated by Ralf Hettinger over 11 years ago
The issue is still valid for 4.7 and the "old", non-experimental version of indexed_search in 6.0+
Updated by Alexander Opitz over 11 years ago
- Status changed from Needs Feedback to New
Updated by Mathias Schreiber almost 10 years ago
- Target version set to 7.5
- Is Regression set to No
Updated by Benni Mack about 9 years ago
- Target version changed from 7.5 to 7 LTS
Updated by Tymoteusz Motylewski over 8 years ago
- Status changed from New to Resolved
fixed with https://review.typo3.org/47476