#111266[BUG] Record list: Visibility toggle missing for non-excluded fields
Description
Problem
In TYPO3 v14, the visibility toggle (hide/unhide action) is missing in the Record List module for non-admin backend users when the TCA exclude property is removed from the visibility field.
The same users can still modify the visibility field in the record editing form and toggle visibility through the context menu.
Steps to reproduce
- Configure a table with a visibility field (
ctrl.enablecolumns.disabled). - Remove the
excludeproperty from the corresponding TCA field configuration. - Log in as a non-admin backend user with write permissions for the table.
- Open the Record List module.
Actual result
The hide/unhide button is missing from the record actions.
Expected result
The hide/unhide button should be displayed when the visibility field does not require explicit field-level access control.
Technical analysis
The permission condition in DatabaseRecordList.php currently uses:
$field->supportsAccessControl()
|| $backendUser->check('non_exclude_fields', $table . ':' . $hiddenField)
This appears inconsistent with the implementation in GridColumnItem::isVisibilityToggling(), which uses:
!$field->supportsAccessControl()
|| $backendUser->check('non_exclude_fields', $table . ':' . $disabledFieldName)
The missing negation causes the visibility toggle to disappear when field-level access control is not required.
Proposed fix
In DatabaseRecordList.php:
- $schema->getField($hiddenField)->supportsAccessControl()
+ !$schema->getField($hiddenField)->supportsAccessControl()
This would align the Record List behavior with the Page Module and ensure consistent field-level permission handling.
Additional considerations
A regression test should verify:
- Non-excluded visibility fields: the toggle is displayed for users with appropriate table permissions.
- Excluded visibility fields without explicit permission: the toggle is not displayed.
- Excluded visibility fields with explicit permission: the toggle is displayed.
Affected versions
TYPO3 v14.x
The issue appears to be a regression compared to TYPO3 v13.4.
Reviews 2
Files 1
History 26
-
Gerrit Code Review pushed patch set 1 for main to change 97208 status
NewUnder Review <span data-processor="relativetime" data-value="2026-10-29T05:59:22+00:00" > 10/29/26, 05:59 </span> -
Gerrit Code Review pushed patch set 2 for main to change 97208 <span data-processor="relativetime" data-value="2026-10-29T12:45:12+00:00" > 10/29/26, 12:45 </span>
-
Gerrit Code Review pushed patch set 1 for 14.3 to change 97220 <span data-processor="relativetime" data-value="2026-10-29T21:49:13+00:00" > 10/29/26, 21:49 </span>
-
Wolfgang Klinger commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-10-29T21:55:12+00:00" > 10/29/26, 21:55 </span> -
Gerrit Code Review pushed patch set 2 for 14.3 to change 97220 status
ResolvedUnder Review <span data-processor="relativetime" data-value="2026-10-29T22:16:58+00:00" > 10/29/26, 22:16 </span> -
Wolfgang Klinger commented and changed status
Under ReviewResolved <span data-processor="relativetime" data-value="2026-10-29T22:35:12+00:00" > 10/29/26, 22:35 </span>Applied in changeset commit:db986f82647efefe6a87cf6e5846df4cc610bec0.
Applied in changeset commit:d819f9e46be3086197c51cbef4ca9de4b4e19372.