Project

General

Profile

Actions

Bug #102578

open

Translated content elements can not be found when the original element is disabled

Added by Daniel Dorndorf 3 months ago. Updated 3 months ago.

Status:
New
Priority:
Should have
Category:
Extbase + l10n
Target version:
-
Start date:
2023-12-01
Due date:
% Done:

0%

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

Description

Hi,

if you create a translated element in connected mode and disable the element in the default language, the translated element won't show up anymore too, even though it still is enabled.

It seems like the record overlay can't be fetched because of the disabled original, so it completely gets ignored.

This issue is has a longer history like an old issue I created for v6.2: https://forge.typo3.org/issues/69022

I really thinks this needs a solution as this is confusing for redakteurs.

Greetings
Daniel


Related issues 1 (1 open0 closed)

Related to TYPO3 Core - Bug #69022: Translated records can't be found when the original is hiddenNew2015-08-13

Actions
Actions #1

Updated by Simon Schaufelberger 3 months ago

  • Related to Bug #69022: Translated records can't be found when the original is hidden added
Actions #2

Updated by Simon Schaufelberger 3 months ago

please add steps how to reproduce this bug.

Actions #3

Updated by Oliver Bartsch 3 months ago

Might be related to #102389?

Actions #4

Updated by Daniel Dorndorf 3 months ago

Simon Schaufelberger wrote in #note-2:

please add steps how to reproduce this bug.

I tried in the description but heres a more detailed version:

  1. Create a translation for a page
  2. Create a content element on that page
  3. Translate the content element to the foreign language in connected mode
  4. Disable the content element in the default language
  5. Open the translated page in the frontend

Now the element even though translated and enabled won't show up.

This is a tough one and I remember this to happen even back to v6.2, I think you would either need to inherit the disabled state to the translated "child" record or have an enabledFields exception in the record language overlay.

Greetings
Daniel

Actions #5

Updated by Jo Hasenau 3 months ago ยท Edited

Actually this should be the expected behaviour of the connected mode, since in connected mode the default language element got the full control over all target language children. So other than adding it (by translation) or deleting it, there should be no option to enable, disable or sort an element in the target language at all.

Same for child elements like sys_file_reference or child elements of any kind of container element. There can only be less elements (untranslated yet) but no additional elements or translations in other positions than in the default language.

If we take the connected mode seriously, there must not be any option to control the translation target element structures other than via the original element structures in the default language.

Actions #6

Updated by Daniel Dorndorf 3 months ago

Hi Jo, thanks for the explenation.

if this is the expected behaviour this would really need a clear visual feedback, like a disabled "disable-button" for example.
I haven't had the case too often but redakteurs working with translations always get confused by this because their expectation is to control this like in the free mode.

Actions

Also available in: Atom PDF