Project

General

Profile

Actions

Feature #60026

open

Set explicitly 'readOnly' sys_language_uid of child to value, taken from parent record

Added by Viktor Livakivskyi over 9 years ago. Updated almost 7 years ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Localization
Target version:
-
Start date:
2014-07-01
Due date:
% Done:

0%

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

Description

After fix of #57063 there is still a case, when record can get sys_language_uid=0.

Whenever 'sys_language_uid' field of child is marked as 'readOnly' in config section, child record again becomes saved with sys_language_uid=0.

This is a common behaviour, since there is no need to allow editors to change language of a localization.
DataMapper needs to set explicitly sys_language_uid to value, taken from parent record, if it doesn't appear in POST and is defined as 'languageField' in 'ctrl' section of TCA.

Technical notes.
If a field is marked as 'readOnly' it is rendered with 'disabled' attribute in HTML, and therefore it's value is not sent to the server. Therefore DataMapper sets sys_language_uid to 0, since nothing comes in POST-request.


Related issues 4 (1 open3 closed)

Related to TYPO3 Core - Bug #57063: Parent language is not applied to new child recordsClosed2014-03-19

Actions
Related to TYPO3 Core - Bug #76048: IRRE: Child records - New record doesn't get language of parent (non localized records but using new button)ClosedJo Hasenau2016-05-04

Actions
Related to TYPO3 Core - Bug #73609: Creating IRRE child element without language of parent elementClosed2016-02-22

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

Actions
Actions

Also available in: Atom PDF