Bug #81996
open
Read ony select field 'renderType' => 'selectSingle' renders all available items
0%
Description
Read only 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.
Updated by Susanne Moog about 7 years ago
- Category set to FormEngine aka TCEforms
Updated by Benni Mack about 5 years ago
- Related to Bug #77257: The selection of a selectbox with the l10n_display type of defaultAsReadonly in TCA is wrong for a localized record added
Updated by Markus Klein over 4 years ago
- Related to Bug #92863: TCA change for sys_file_reference l10n_parent kills performance added
Updated by Sybille Peters about 4 years ago
- Related to Epic #93547: Collection of problems with large sites added
Updated by Christian Eßl about 2 years ago
- Related to Task #100109: Superfluous access permission checks in InlineRecordContainer and FileReferenceContainer added
Updated by S P 2 months ago
· Edited
The conflict here is, that a potential displayCond should have all items available. The existence of a displayCond could 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).
Updated by Simon Schaufelberger 2 months ago
- TYPO3 Version changed from 13 to 12
please do NOT change this to the newest version because it also applies to 12.