This is a placeholder for interest in porting this module to D7. Should be fairly simple, and if there's interest I may even help out. Also this adds the possibility of expanding support to attach a filedrop to not just nodes, but all entity types.
This is a placeholder for interest in porting this module to D7. Should be fairly simple, and if there's interest I may even help out. Also this adds the possibility of expanding support to attach a filedrop to not just nodes, but all entity types.
Comments
Comment #1
jason.fisher commentedI have no immediate use but I like this concept. Groups work differently, but that may be a good thing. Perhaps this could live as a Feature in D7 without needing much/any custom code?
Comment #2
techninja commentedI've considered it, though as far as fields on entities go, the "drop" locations are virtual and restricted. Custom code would have to be used to differentiate where it's being used or for what purpose. Honestly, the overhead is so slight and the use-case so specific that I doubt it's worth the trouble to attempt to make a features module out of it.
Not to discourage any willing thrill-seekers mind you. ;)
One of the original plans was to allow attachment of Filedrop on a lot more than just node types, with D7 entities, "attachment" to comments, users or otherwise would be made far simpler and allow for quite a bit more, though the use cases get a bit fuzzy after comment attachments...
Comment #3
Grayside commentedThe privacy handling would also be a lot simpler. A Filedrop "field" could be configured to use any available Stream Wrapper.
I don't think Filedrop could really be a feature, though if we started adding configuration a more sophisticated level of exportability may be called for.
D7 fields as-is don't work, because the filedrop is visually attached to a targeted entity, but not actually content to be stored as part of that entity.