can we restrict Page assets shown in Content Finder to match available cq drop targets?

we have defined component accepts drag-and-drop of user content, , cq:droptargetconfig node (under cq:editconfig > cq:droptargets) defines groups=[page] because accepts assets of type cq:page not images.  our component copy of /libs/foundation/components/image component, because accepts drag-and-drop, , modified innards accept cq:page not image.  seems 'accept' property ignored when groups=[page], think 'accept' processed when groups=[media] i.e. images.

 

this working fine except there user content time-consuming users select right pages drag content finder extension drag-and-drop target.  , if pick wrong kind of asset can mess target page.  there many types of components based on cq:page , many of them not belong in particular drop target, if user drags inappropriate asset our drop target cq allows it, disastrous results (content properties , nodes overwritten in wrong place, etc).

 

yes content finder has search bar restrict list of assets shown there without user having type in search term.  hope there page-based content analogous 'allowedpaths' property in template.  in wcm when click new page @ jcr path, template-chooser dialog comes , has templates allowed jcr path, dialog uncluttered , guides user relevant template.  similarly, components have 'allowedparents' property can't use them don't belong.  please advise if there similar make easier find relevant content in content finder tab pages.

More discussions in Archived Spaces

adobe