Bug #92768

Extbase: Localized Children records are not working when parent element has sys_language_uid=-1

Added by Alex Kellner 8 months ago. Updated 3 months ago.

Status:
Needs Feedback
Priority:
Should have
Assignee:
-
Category:
Extbase
Target version:
-
Start date:
2020-11-04
Due date:
% Done:

0%

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

Description

Hi guys,

While upgrading TYPO3 (from 8 to 10) website of $university we are facing some strange localization behaviours.
In this case, we try to localize children records (in own extbase plugin) while parent elements have a language setting "all". Localization is not possible any more (means: the labels are not shown in frontend in the additional language). We would have to localize also every parent record in all languages that are needed for children records (even if database values are the same).

I also experienced the same issue with powermail records in the latest TYPO3 10.4.9. Changing the fallback mode in site configuration for the additional languages seems to have no effect here.

Greetings, Alex


Related issues

Related to TYPO3 Core - Bug #92757: Localization from language "All" should not be possibleClosed2020-11-03

Actions
#1

Updated by Alex Kellner 8 months ago

  • Description updated (diff)

Update to clearify

#2

Updated by Georg Ringer 8 months ago

  • Related to Bug #92757: Localization from language "All" should not be possible added
#3

Updated by Georg Ringer 8 months ago

  • Status changed from New to Needs Feedback

Thanks for creating the issue. I guess it is related to #92757. IMO localization should not be possible for records with language set to all, does that make sense to you?

#4

Updated by Alex Kellner 8 months ago

Thx for asking Georg.

I just reflected with the customer (just for your information: Communication department of a University which manage 2300 editors for 60K pages).
Ok, on the one hand it is a breaking change while upgrading, but on the other hand it's hard to understand why it should not be possible that records can not be translated only because the parent is set to "all languages" (from an editor point of view).

Alex

#5

Updated by Dmitry Dulepov 3 months ago

Alex Kellner wrote in #note-4:

Ok, on the one hand it is a breaking change while upgrading, but on the other hand it's hard to understand why it should not be possible that records can not be translated only because the parent is set to "all languages" (from an editor point of view).

It is described in the documentation (https://docs.typo3.org/m/typo3/guide-frontendlocalization/master/en-us/LocalizedContent/Index.html#the-all-language):

When using overlays, it becomes possible to use a particular language called “All”, which will be automatically visible across all translations. The uid of that particular language is “-1”. Note that no “Translate” button appears, the new content element is valid for all languages.

I am not sure how you translate it but you definitely not using TYPO3 translation algorithm because TYPO3 will refuse to localize from language with uid=-1. So I believe you have an error in your code. Language "All" is not translatable and it was never translatable. Please, fix your code.

This is not a bug in TYPO3. Sorry.

#6

Updated by Jonas Eberle 3 months ago

While it should not be possible, it still is in 2 ways which both lead to an inconsistent database:

1)
  • Create content in default language
  • Translate
  • Set default content to [All languages]
2)
  • Create content as [All languages]
  • Create content in translated language
  • Set "Transl. Orig." field to the [All languages] content

I think at least 2) should be easy to fix.

#7

Updated by Dmitry Dulepov 3 months ago

Language "All" is not translatable by design. Have a look to the docs.

#8

Updated by Jonas Eberle 3 months ago

Dmitry Dulepov: it should not, but it is. It won't work and will of course have all kinds of unexpected side effects but editors can create such a bad state. We could (and should IMHO) improve DataHandler and Backend UI to prevent that.

#9

Updated by Dmitry Dulepov 3 months ago

Jonas Eberle wrote in #note-8:

I fully agree with fixing value combinations that should not appear!

Also available in: Atom PDF