#81996Read-only select field 'renderType' => 'selectSingle' renders all available items
Description
Readonly select field with ‘renderType’ => ‘selectSingle’ renders all available items in the select box.
Instead, only currently selected item should be rendered. This influences performance when there are many available elements.
Reviews 1
Related issues 4
- Bug #77257The selection of a selectbox with the l10n_display type of defaultAsReadonly in TCA is wrong for a localized record
- Bug #92863TCA change for sys_file_reference l10n_parent kills performance
- Epic #93547Collection of problems with large sites
- Task #100109Superfluous access permission checks in InlineRecordContainer and FileReferenceContainer
History 1113
-
Susanne Moog changed category <span data-processor="relativetime" data-value="2018-01-24T20:24:22+00:00" > 01/24/18, 20:24 </span>
-
Benni Mack changed Related to #77257 <span data-processor="relativetime" data-value="2020-03-14T16:34:18+00:00" > 03/14/20, 16:34 </span>
-
Sybille Peters changed Tags performance <span data-processor="relativetime" data-value="2020-10-26T16:33:10+00:00" > 10/26/20, 16:33 </span>
-
Markus Klein changed Related to #92863 <span data-processor="relativetime" data-value="2020-11-17T18:46:20+00:00" > 11/17/20, 18:46 </span>
-
Sybille Peters changed Related to #93547 <span data-processor="relativetime" data-value="2021-02-19T07:00:46+00:00" > 02/19/21, 07:00 </span>
-
Christian Eßl changed Related to #100109 <span data-processor="relativetime" data-value="2023-03-07T12:27:21+00:00" > 03/07/23, 12:27 </span>
-
S P commented and changed TYPO3 Version
713 <span data-processor="relativetime" data-value="2025-01-09T10:06:20+00:00" > 01/09/25, 10:06 </span>Still valid on v13
-
Simon Schaufelberger commented and changed TYPO3 Version
1312 <span data-processor="relativetime" data-value="2025-01-09T11:10:44+00:00" > 01/09/25, 11:10 </span>please do NOT change this to the newest version because it also applies to 12.
-
S P commented and changed TYPO3 Version
1213 <span data-processor="relativetime" data-value="2026-06-11T07:27:08+00:00" > 06/11/26, 07:27 </span>Still valid on v14. (changing this ticket at least to v13 now, since v12 won’t get this for sure as it is now ELTS – actually even v13 won’t get this as will, becaue it is in Priority Bugfixing phase, and this here is for sure no prioritybug fix)
-
S P changed subject
Read ony select field 'renderType' => 'selectSingle' renders all available itemsRead-only select field 'renderType' => 'selectSingle' renders all available items description <span data-processor="relativetime" data-value="2026-06-11T07:28:09+00:00" > 06/11/26, 07:28 </span> -
Gerrit Code Review pushed patch set 1 for main to change 96110 status
NewUnder Review <span data-processor="relativetime" data-value="2026-09-27T10:03:24+00:00" > 09/27/26, 10:03 </span> -
Gerrit Code Review pushed patch set 2 for main to change 96110 <span data-processor="relativetime" data-value="2026-10-24T09:14:56+00:00" > 10/24/26, 09:14 </span>
The conflict here is, that a potential
displayCondshould have all items available. The existence of adisplayCondcould however be checked as well when rendering such a field (readonly && !displayCond).To workaround your performance issue you can add a
foreign_table_where, however yourself:AND foreign_table_name.uid = ###REC_FIELD_yourfieldname###This will have the effect you need. I do this all the time, for example on the parent backreference field of inline relations (if you have such a field in the TCA of the child table, e.g. to map it to Extbase, then the core will run a full
select *for each inline relation in the backend GUI, which can be even worse than a simple readonly select field).