TYPO3 Core

please add steps how to reproduce this bug.

Might be related to #102389?

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

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.

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.