Bug #63092
Inline/IRRE records: language field of child records is not updated when modifying parent language field - e.g. problematic for sys_file_reference
| Status: | New | Start date: | 2014-11-20 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | - | % Done: | 0% |
|
| Category: | - | Spent time: | - | |
| Target version: | next-patchlevel | |||
| TYPO3 Version: | 6.2 | Is Regression: | No | |
| PHP Version: | Sprint Focus: | |||
| Complexity: |
Description
When I have IRRE records and I modify the language field, e.g. to set it from "0" to "-1" the child records are not updated to that language field but are kept at the ones during creation.
Except "-1" that one never seems to be used.
This can be problematic under certain circumstances, e.g. extbase will not deliver the file anymore via the datamapper as the language of the sys_file_reference is not included.
Related issues
History
#1 Updated by Andreas Allacher 9 months ago
This might be related to some others but the others do not exactly describe this behaviour but might be a result of this.
To auto-change this field might only be interesting under certain circumstances, e.g. if hideTable is active and the language field is not visible (hidden palette).
#2 Updated by Andreas Allacher 8 months ago
It is even worse when creating a new record, e.g. I create a content element and change the language to non default, the sub-records (e.g. case images) will not have the selected language but the default value (if available, otherwise it has the first available value).
#3 Updated by Andreas Allacher 8 months ago
Also if the parent record is set to all language (-1) it the child record will be set to default language, even if the child record is a new record and the parent record is already existed because the select is like this:
if ($parentRecord[$parentLanguageField] > 0) {
$record[$childLanguageField] = $parentRecord[$parentLanguageField];
}
#4 Updated by Andreas Allacher 6 months ago
Just wanted to ask if I need to provide additional information or has there already be something done in regards to this?
#5 Updated by Jo Hasenau 25 days ago
- Target version set to next-patchlevel
Just came across that issue while looking for a solution of sorting problems in translated records.
IMHO a parent record with a language set to "all" should be allowed to contain elements with all available language settings. So switching the children to "all" as well would be unexpected at least for my personal taste.
In any other case children should of course be switched to the selected language, since otherwise they will just diseappear in BE and/or FE views.
#6 Updated by Andreas Allacher 24 days ago
So you mean the possibility to have the container for all languages but the sub elements for certain languages only?
That might already be an issue in how to display it in the page view.
In any case, even if we allow this, the default setting should still be "-1" for child records and it should at least be possible to create those and not set default to 0
Even if someone were to change thme later on.
Also most users don't have access to the language selector for a record directly, so they can not really select the language here at all.