Default language not always honored in result list (has patch)
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)
Updated by Ralf Hettinger over 11 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.