Quick question: This module is cool but wouldn't it be better to use the fid in the link instead of the nid so that each node can support multiple files, and so that files can be stored in a normal "page" node? Do you see pitfalls with this system? I ask because my organization might want to make some time for me to modify your module to work this way. Maybe I could create an interface so users can choose between the two.
Thanks,
Moses

Comments

rupl’s picture

rupl
he/him
Primary language English
CreditAttribution: rupl commented
Version: 7.x-1.0 » 7.x-1.x-dev

We had originally built the module with the assumption that there's a 1:1 relationship between nodes and files. Think of it in terms of building a library of files in Drupal. In order for each file to have a full description, search result entry, etc, you would make a new File node for each file, but retain all versions of that file in one node (using the built-in node revisions).

But, as with many approaches to building models in Drupal, it's all about your business/implementation needs. If you have the need and desire to build a second approach into the module, you're welcome to submit patches and we can review it.

Don't worry if you find yourself needing to change stuff (even in terms of DB schema). We can figure out if we need to bump the module to 2.0 after we've got a working patch here.