Feature #99724
closed
Add possibility to search for ds_pointerField in rootline of current table
0%
Description
The following TCA does not work without using a Hook to resolve the dataStructure:
"config" => [
"type" => "flex",
"ds_pointerField" => "backend_layout",
"ds_pointerField_searchParent" => "pid",
"ds_pointerField_searchParent_subField" => "backend_layout_next_level",
]
The fields ds_pointerField_searchParent and ds_pointerField_searchParent_subField are only taken into account, if the dataStructure is defined in another table.
Updated by Christian Kuhn about 1 year ago
- Related to Task #102224: Avoid TemplaVoila related FlexForm details added
Updated by Christian Kuhn about 1 year ago
- Status changed from New to Rejected
Hey.
I don't think we should do this: We actively removed support for ds_pointerField_searchParent and its friends with #102224 to reduce complexity of some very rarely used TCA capabilities.
To my perception, the lookup logic based on 'ds' and 'ds_pointerField' is what is typically used, most notably by tt_content of course.
If you really need to have "more" for whatever reason, the events in getDataStructureIdentifier() and parseDataStructureByIdentifier() give you all the flexibility to manipulate the DS lookup with a lot of freedom.
I hope it's ok to close here as 'rejected'. Please ping us if you don't agree and still see broad use cases for extending the default DS lookup mechanism in core.