Issue Bug Closed

#72287Localization-handling not understandable

Jeff C 12/17/15, 11:08 updated 03/21/16, 12:31

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.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.