Hide Nested Content Elements in List View

[nhovratov]

Content Blocks has a feature called "Nested Content Elements" which makes in possible to nest Content Elements, while the Child-Elements are hidden in the Page View and are not rendered twice in the Frontend.

There is still one place, which doesn't hide them: List View.

This can be confusing, as it doesn't reflect the elements in the Page View, especially for Editors. They might delete them, thinking these are wrong.

It would be possible to generally hide them with existing Content Blocks API and an PSR-14 Event in TYPO3. However, there are cases in which it is desired to list those nested elements in the List View. For example there is an Accordion Element and the child items should be link-able. If we would hide those items, it wouldn't be possible anymore to select them in the Link Wizard. An idea would be to allow an opt-out of this new default behavior via a property in the Collection FieldType.

[jonaseberle]

I would vow to keep them always shown in the List module.
I would expect that to be the default there for all records, regardless if it is nested or not.
In my opinion the List module can be seen as an "advanced" function for content elements and is rather used for debugging or mass deletion – I think it makes sense to show all content elements there.

[nhovratov]

@jonaseberle In my case a customer had a problem that his editors have access to the List Module and were confused about the additional Content Elements, which weren't visible in the Page Module. Then deleted them and complained why their content is missing... I don't think this is a debug view, but a real place editors use to edit content "quickly".

[asakurayoh]

It would make sens tto see them "embed" it their parent content. It's not possible currently but that would make the most sens. Also, the reordering is probably problematic currently with those content, in List view, no?.
Same with Category that are weird in List View, why did we not have a special view for them? Ok, I know, out of scope of here, but more about a kind of "parent relationship".

[mkroener]

gridelements had/has a nesting feature for the List View where the content elements are nested in the list view under the grid element they belong to
This would make it clear for editors that these content elements belong to another element.
But it would probably also require changes in the core to be viable gridelements currently uses a XClass for this