Issue Bug Closed

#95996TCA columns type inline overrideChildTca CType dosen't get recognized correctly.

Tobias Ulber 11/16/21, 12:25 updated 06/20/24, 10:35

Description

I have created a inline Element that should only hold elements of CType text. With Typo3 version 11 this is not working anymore:

<?php

$GLOBALS['TCA']['tt_content']['columns']['text_tab_text_elements'] = [
    'config' => [
        'appearance' => [
            'collapseAll' => '1',
            'enabledControls' => [
                'dragdrop' => '1',
            ],
            'levelLinksPosition' => 'top',
            'showAllLocalizationLink' => '1',
            'showPossibleLocalizationRecords' => '1',
            'showSynchronizationLink' => '1',
            'useSortable' => '1',
        ],
        'foreign_sortby' => 'sorting',
        'foreign_table' => 'tt_content',
        'overrideChildTca' => [
            'columns' => [
                'colPos' => [
                    'config' => [
                        'default' => '999',
                    ],
                ],
                'CType' => [
                    'config' => [
                        'default' => 'text',
                    ],
                ],
            ],
        ],
        'type' => 'inline',
        'foreign_field' => 'text_tab_text_elements_parent',
    ],
    'exclude' => '1',
    'label' => 'LLL:EXT:sitepackage/Resources/Private/Language/Backend.xlf:text_tab_text_elements.label',
];

If I create a new element that is using the text_tab_text_elements column and then create a child relation, the element renders the CType text form elements. But in the CType selectbox, the CType that is selected is not text. Text is not even appearing in the CType selectbox. After saving the records CType of the child elements is not text in the database.

Im not sure if this is a bug or if something changed in Typo3 11. This code works perfectly in Typo3 10. If something has changed in Typo3 11 there should be a TCA migration hint.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.