Issue Bug New Stale

#110095TcaColumnsRemoveEmptyRelations behavior is too disruptive

Oliver Hader 06/24/26, 10:30 updated 06/24/26, 10:44

Description

The default behavior of the newly introduced feature to completely hide select fields (and others) in the backend form in case not selectable items can be shown is too disruptive. In case the debug-mode is not active, an expected field is simply missing in the backend form, leaving the user clueless and confused what actually happened.

Step to reproduce

  • new TYPO3 v14/v15 instance (not having filemounts or be_groups at all)
  • TYPO3_CONF_VARS/BE/debug is disabled (false)
  • create a new be_groups record
  • the fields “subgroup” or “filemounts” are simply not shown (the “filemounts” has wizard actions for creating new file mounts

Expectation

  • at least show a hint, why the field is not shown (like it’s done when having debuggin enabled)

Suggested Change

Instead of enforcing the disruptive change and that affected fields have to opt out (which also is a breaking change), I’d suggest to apply the opposite behavior:
Fields must actively opt in, in case the want to use that TYPO3 v14.2 feature.

Docs Reference

Reviews 0

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

Fix this issue

Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch

Commit message
[BUGFIX] TcaColumnsRemoveEmptyRelations behavior is too disruptive Resolves: #110095 Releases: main