TYPO3 Core

This is also broken for 6.2

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/49668

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/49668

Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/49668

Hi Lukas,

this indeed looks like a change in behavior. But the search is now more predictable for the editors than before.
In your use-case the translations are shown because the record of the default language matches your search and not because the translated record matches your search.

Groet Frans

Frans Saris wrote:

Hi Lukas,

this indeed looks like a change in behavior. But the search is now more predictable for the editors than before.
In your use-case the translations are shown because the record of the default language matches your search and not because the translated record matches your search.

Groet Frans

can someone explain me why line 771 in DatabaseRecordList.php was Changed during this BugFix ?

before this patch:
if ($this->localizationView && $l10nEnabled ) {

after this patch:
if ($this->localizationView && $l10nEnabled && $this->searchString === '') {

All other changes in that patch looks logical to me, but this change, changes the behavior:

in my Case:
a backend editor wants to change the image of a specific translated entry, in the past he could search for a word in the default language and had, in localisation View, all Translated Records of this search hit attached.

So he does not need to know the translation of his search word in Russian (what he does not understand) but is able to change the image in all Translations of this. Now he hast do do (with 8 translations) do 8 Searches or needs to know the ID

Reverting just this line, i get back the old behavior and also this bug #77664 is fixed a nd i cant see a negative effect.

That check is there to prevent that a record is shown 2 times.
1st time because the search matched, 2th because the translated record is added there

Thanks for the confirmation.
Yesterday i though that this situation will not happen, but i build a scenario and you are right.

I explained it to the backend editor and he accepted the new situation ...