Bug #88966

Backend translation of contents should show warnings related to defined fallbackType from Site Configuration

Added by Tobias Gaertner about 1 month ago. Updated 27 days ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Localization
Target version:
-
Start date:
2019-08-16
Due date:
% Done:

0%

TYPO3 Version:
9
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

There are currently 3 types for Frontend: strict, fallback and free.

In Backend there are two modes: connected (translate) and free (copy), (and mixed if you count that).

Problem is that they are independent and very misleading to editors in certain setups. For example: if we define the fallbackType: free, backend still shows red warings if we mix both modes in backen - what is totally fine for the frontend.
Or we define fallbackType: fallback and create only free translated contents in backen - no warning, but in frontend no translation is shown but the default contents.

I think the warnings in Backend should be related to the fallbackType set.

History

#1 Updated by Riccardo De Contardi 27 days ago

  • Category set to Localization

Also available in: Atom PDF