0 Replies Latest reply on Apr 24, 2013 7:57 AM by hrietz

    Drag & drop creates download component without nt:file node - Why? Can that be changed?


      Hi everybody,

      I have noticed, that dropping a file from the file system into a parsys will create a foundation download component which differs in structure from the ones created manually. The latter all have an nt:file node, the former does not create such a node, just the nt:resource node. I think, this is bad, because searches usually target the nt:file nodes. So files, which have been dropped directly from the filesystem, can not be found by the standard search implementations.

      Can the structure created by D&D by configured/changed somerwhere (kind of easily)?