Issue Bug Closed

#85456columnsOverrides not possible for type group

Daniel Siepmann 07/02/18, 17:38 updated 09/07/26, 20:33

Description

It’s not possible to overwrite configuration of columns of type group via columnsOverrides.
It partially works, but not for the data source.

Due to configuration in formEngine.formDataGroup.tcaDatabaseRecord the order is wrong.

\TYPO3\CMS\Backend\Form\FormDataProvider\TcaColumnsOverrides::class is called after \TYPO3\CMS\Backend\Form\FormDataProvider\TcaGroup::class.
While it would be easy to adjust order, it’s in fact not. TcaColumnsOverrides does need \TYPO3\CMS\Backend\Form\FormDataProvider\DatabaseRecordTypeValue which in turn needs \TYPO3\CMS\Backend\Form\FormDataProvider\TcaGroup::class again.

This way one can not re-use the records column of tt_content for any other record. While it works while selecting entries, it does not work either for suggest nor for re-display in backend. As always the original tt_content records are fetched for persisted IDs.

Reviews 0

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

History 3

  1. Georg Ringer commented and changed status New Closed <span data-processor="relativetime" data-value="2026-09-07T20:33:12+00:00" > 09/07/26, 20:33 </span>

    (AI based review, so if still valid please open a new issue or reach out to me)

    Checked against current main (15.0-dev). This looks resolved, both the reasoning
    and the symptom.

    The ordering argument from the report no longer applies. I resolved the actual
    execution order of the “tcaDatabaseRecord” form data group (the result of
    DependencyOrderingService::orderByDependencies(), not the array order in
    DefaultConfiguration.php):

    DatabaseRecordTypeValue   position  9
    TcaColumnsOverrides position 27
    TcaGroup position 41 (of 61)

    So TcaColumnsOverrides already runs before TcaGroup. And DatabaseRecordTypeValue
    now only depends on DatabaseRowDefaultAsReadonly, not on TcaGroup, so the
    circular constraint that blocked a fix back then does not exist anymore.

    I also verified it functionally: I overrode tt_content.records (type=group) via
    columnsOverrides for CType “text” to allowed = pages and compiled a real record
    through the full provider stack. Result:

    recordType               “text“
    allowed in processedTca “pages“
    databaseRow[‘records’] [{table: “pages”, uid: 1, title: “…”}]

    That is exactly what the report says does not work (“As always the original
    tt_content records are fetched for persisted IDs”): the persisted id is now
    resolved against the overridden table.

    The suggest wizard is covered as well. SuggestWizardController determines the
    record type and takes the field configuration from the sub schema:

    if ($recordType !== null && $schema->hasSubSchema($recordType)) {
    $fieldConfig = $schema->getSubSchema($recordType)->getField($fieldName)->getConfiguration();
    }

    To be precise about what I actually ran: the re-display case above was executed
    as a test, the suggest part I only verified by reading the code.

    I suggest closing this. Retesting on v8 is pointless, it is EOL and the provider
    chain has been reworked several times since. Worth referencing #101435
    (commit 4930c561853, January 2026), which pulled columnsOverrides support into
    the DataHandler operations; it is already linked as “relates”.