Project

General

Profile

Actions

Bug #88966

open

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

Added by Anonymous almost 5 years ago. Updated over 4 years ago.

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

0%

Estimated time:
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.


Related issues 1 (1 open0 closed)

Related to TYPO3 Core - Story #101564: User Interface related translation issuesNew2023-08-03

Actions
Actions #1

Updated by Riccardo De Contardi over 4 years ago

  • Category set to Localization
Actions #2

Updated by Jo Hasenau 10 months ago

  • Related to Story #101564: User Interface related translation issues added
Actions

Also available in: Atom PDF