Project

General

Profile

Actions

Bug #81994

closed

Indexed Search Bugfix #30852 messes with Realurl cache

Added by Jan Rödig over 6 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Indexed Search
Target version:
-
Start date:
2017-07-28
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
8
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

The "new" behaviour of Indexed Search adding "L=0" parameter even on pages with only a single language messes with Realurl cache.
See last comments on Bugfix #30852. Also: https://github.com/dmitryd/typo3-realurl/pull/461

The best solution would be, if you could turn off this behaviour via typoscript config.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #30852: Multilingual search in translated pages: Results of default language always linking to current language Closed2011-10-12

Actions
Actions #1

Updated by Tymoteusz Motylewski over 6 years ago

  • Status changed from New to Needs Feedback

Hi
the issue you've linked is wrong 30582.
AFAIK it is correct to pass L=0 in the url.
EXT:solr does the same thing.

Why do you think it is a core bug?

Actions #2

Updated by Jan Rödig over 6 years ago

Tymoteusz Motylewski wrote:

Hi
the issue you've linked is wrong 30582.
AFAIK it is correct to pass L=0 in the url.
EXT:solr does the same thing.

Why do you think it is a core bug?

Hm, perhaps "feature request" (?). You can of course change it, if this would fit better.
Of course you're right, I twisted the numbers, my bad.

Anyway, about the issue:
In a single language Typo3 install with indexed search and realurl adding the language parameter will lead to "random" domain.tld/realurl/path/?L=0 entries in menus etc.
In a multilanguage install you won't have this problem, as you'd map the language parameter to pathsegments in realurl config.

Prior to the mentioned bugfix this did not happen. I see why this fix was done, but still the proper way would imho be to be able to override this behaviour for single language installs. I don't see why the parameter would be needed in this case.

Actions #3

Updated by Jan Rödig over 6 years ago

  • Description updated (diff)
Actions #4

Updated by Mona Muzaffar over 6 years ago

  • Related to Bug #30852: Multilingual search in translated pages: Results of default language always linking to current language added
Actions #5

Updated by Alexander Opitz over 6 years ago

  • Status changed from Needs Feedback to New
Actions #6

Updated by Georg Ringer over 6 years ago

  • Status changed from New to Resolved

resolved with #81164

Actions #7

Updated by Benni Mack over 5 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF