Project

General

Profile

Actions

Bug #61871

closed

Copy option for all language elements is available if mod.web_layout.defLangBinding is set

Added by Andreas Allacher about 10 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2014-09-25
Due date:
% Done:

0%

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

Description

I guess since the change to fix
https://forge.typo3.org/issues/42768

I have no the option to "copy" all language content elements if mod.web_layout.defLangBinding is set (latest git TYPO3 6.2 branch).

Also I don't think it is a good idea to remove the issue but undoing the change to display all language content elements in sublanguages (because that was actually nice, especially because that way one can be sure of the correct ordering of texts).


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #42768: multilanguage content elements (language "all") not shown anymore if defLangBinding is usedClosed2012-11-07

Actions
Related to TYPO3 Core - Feature #66116: defLangBinding = 1 and Copy all non translated content elementsClosed2015-03-28

Actions
Actions #1

Updated by Markus Klein about 10 years ago

Why do you want to copy "all language" CEs?

Actions #2

Updated by Andreas Allacher about 10 years ago

I do NOT want to copy them.
The problem is that there is the option to copy/localize them in the page module if I set
mod.web_layout.defLangBinding = 1

With copy I mean the option in the page module where I can copy elements to localize them.

Actions #3

Updated by Markus Klein about 10 years ago

Ok, I misunderstood your text then.

Clearly the button should not be there.

Actions #4

Updated by Markus Klein about 10 years ago

  • Status changed from New to Accepted
Actions #5

Updated by Markus Klein about 10 years ago

Removing the button though, will make it more difficult to override such a CE for a specific language.

Actions #6

Updated by Andreas Allacher about 10 years ago

Personally I think it would be better to make it work as previously without the change in bug #42768 but make sure the bug itself is fixed (instead of using the workaround in the bug).
I think then this issue should be fixed too.

Actions #7

Updated by Mathias Schreiber over 8 years ago

  • Status changed from Accepted to Closed

implemented in 7.6 LTS

Actions

Also available in: Atom PDF