Project

General

Profile

Actions

Bug #72287

closed

Localization-handling not understandable

Added by Jeff C over 8 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Localization
Target version:
-
Start date:
2015-12-17
Due date:
% Done:

0%

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

Description

We've upgraded to TYPO3 7.6.1 and our client's content editors noticed, that they cannot add content elements in non-standard languages anymore.

I quickly discovered the "problem": As soon as there is a single translated record with link to a standard language element it is not allowed anymore to add content elements that only exist in a non-standard language. When there are no translated content elements one can add as many non-standard language content elements as one likes.

I think I can grasp the idea behind this: Prevent chaos and separate strictly between pages with translated content and pages without. The new localization-wizard emphasizes this separation.

However, we created this not yet released website with our client in a workflow where both ways of translation can coexist. Upgrading now is a huge problem for the content editors.

I don't want to be the nostalgic person that glorifies the past and I understand the many many problems that TemplaVoilá had, but one has do admit that the localization-handling was spot on. A behaviour that since is missed badly by all of our clients.

Actions #1

Updated by Andreas Kienast over 8 years ago

Hi,

you're right with your conclusion. TYPO3 now let's you create either translated content or independent content, you can't mix translations and independent content elements.

There is a flag that allows you again to create such a setup. However, we will make TYPO3 more restrictive about multi-language content with CMS 8, because the current state is error prone with its thousands of configuration settings.

Actions #2

Updated by Andreas Kienast over 8 years ago

  • Status changed from New to Needs Feedback
Actions #3

Updated by Jeff C over 8 years ago

Setting the flag works for now. I'm really curious how translation-handling will be solved in future versions.

Actions #4

Updated by Jigal van Hemert about 8 years ago

  • Status changed from Needs Feedback to Closed

Closed because the configuration is reported to work. Localization handling in v 8 will evolve in the near future.

Actions

Also available in: Atom PDF