New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch content selector to default tree-structure #4933
Comments
+1 for also adding this to Image Selector, equally important to have it there too. It's almost hopeless to text-search in 1000+ item archives of images and content. |
@Bellfalasch It's a bit more complicated for image selector since there we should make sure that parent nodes are not selectable and add deep filtering of nodes that don't have any image content. But we'll get there. |
Doh, worth a shot =) At least having it added to ContentSelector is good progress. As you saw on meetup, both of these are highly requested by users. @alansemenov |
create issue item selector fixed.
create issue item selector fixed.
Everybody loves tree-structure inside content selector in the Move dialog, so we should make this default behaviour.
NB! Since content selector can have different kinds of filtering applied to it (
allowPath
,allowContentType
), we should make sure that we always show nodes that have children, but don't let them be selected (don't render checkbox for multi-select and don't handle the click for single-select) if they are not allowed by filters. Nodes that don't have children and are not allowed by filters should not be shown in the tree.To enable having current "flat" structure, implement support of a config option
flat
:The text was updated successfully, but these errors were encountered: