Project

General

Profile

Actions

Feature #41448

closed

Allow to force sys_language_uid to "All" for new records in the default language

Added by Stefan Galinski about 12 years ago. Updated 5 months ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
Localization
Target version:
-
Start date:
2012-09-28
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Currently it's not possible to force the language field of new records to "All" (TCAdefaults.tt_content.sys_language_uid = -1) for records in the default language. The field value is always overwritten by the incoming default wizard data (class.t3lib_transferdata.php).


Related issues 2 (2 open0 closed)

Related to TYPO3 Core - Epic #93291: Remove sys_language_uid=-1New2021-01-14

Actions
Related to TYPO3 Core - Epic #101557: Translation Handling FindingsNew2023-08-03

Actions
Actions #1

Updated by Mathias Schreiber almost 10 years ago

  • Target version set to 7.4 (Backend)
Actions #2

Updated by Susanne Moog over 9 years ago

  • Target version changed from 7.4 (Backend) to 7.5
Actions #3

Updated by Benni Mack about 9 years ago

  • Target version deleted (7.5)
Actions #4

Updated by Riccardo De Contardi about 7 years ago

  • Category set to Localization
Actions #5

Updated by Riccardo De Contardi over 4 years ago

This issue seems still present on 10.4.0-dev (latest master)

Actions #6

Updated by Benni Mack over 4 years ago

Of course, the new content element wizard hands in a defined "sys_language_uid" parameter due to sorting & language & colPos constraints. I highly recommend to avoid language=-1 everywhere, instead we should fine better solutions in Core to overcome the need for sys_language_uid=-1

Actions #7

Updated by Riccardo De Contardi over 3 years ago

  • Related to Epic #93291: Remove sys_language_uid=-1 added
Actions #8

Updated by leon jänicke over 1 year ago

  • Related to Epic #101557: Translation Handling Findings added
Actions #9

Updated by Benni Mack 5 months ago

  • Status changed from New to Rejected

See my comment 4 years ago. Nowadays there is also a translation initative ensuring to get rid of "-1" as DB value.

I will close this issue now. If you feel this is the wrong decision, let me know and I can re-open the issue.

Actions

Also available in: Atom PDF