Project

General

Profile

Actions

Bug #86738

closed

Translating content elements in free mode works not correcly

Added by Chris Müller over 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Localization
Target version:
-
Start date:
2018-10-25
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
9
PHP Version:
7.2
Tags:
Complexity:
Is Regression:
Sprint Focus:
On Location Sprint

Description

In TYPO3 9.5.0 I am using the newly introduced site configuration. The translations are in free mode. Now I have a page with an English and a German translation and on that page a content element, which is translated in free mode:

Now I open the English content element. It is possible to create a new German translation in the option box on top of the page:

This is not correct, I'm having already a translation.

When I select this option, an error is given:

Perhaps is this bug related to #86627, which doesn't show translations in free mode at all in version 9.5.0.


Files

contentelements.png (16.9 KB) contentelements.png Chris Müller, 2018-10-25 08:48
contentelements2.png (15.7 KB) contentelements2.png Chris Müller, 2018-10-25 08:51
contentelements3.png (7.87 KB) contentelements3.png Chris Müller, 2018-10-25 08:53
Actions #1

Updated by Chris Müller over 5 years ago

  • Description updated (diff)
Actions #2

Updated by Susanne Moog over 5 years ago

  • Sprint Focus set to On Location Sprint
Actions #3

Updated by Jasmina Ließmann over 5 years ago

I can confirm this behaviour. It occurs if you chose to copy the content elements of the default language into the second language.

If you created a translated content element without the translation wizard (neither 'translate' nor 'copy') it is possible to create a translation of the default content element (here "English page" as a german translation), but after this the page is in a mixed mode, because of the connection of the two content elements.

Actions #4

Updated by Chris Müller about 5 years ago

This bug can be closed, as it is was fixed since 9.5.0.

Actions #5

Updated by Riccardo De Contardi over 4 years ago

  • Status changed from New to Closed

Thank you for your reply and sorry for having neglected this one for so long. Closing it.

If you think that this is the wrong decision please reopen it or ping me.

Actions

Also available in: Atom PDF