Multiple Roots and Multiple dbfms
gmclelland - April 24, 2008 - 20:13
| Project: | DataBase File Manager |
| Version: | 5.x-3.1 |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Not sure if this is possible, but it would be cool if this module was able to specify:
- A default root directory setting for each content type.
- A default root directory setting for users - to give each user their own personal file space.
- A default root directory setting for each organic group.
- A root directory setting for each WebFM cck widget.
Each root directory setting could use an existing folder in the WebFM folder tree as it's root. You cannot see or move up the root directory tree.
I guess to do all of this, you would have to implement multiple WebFM directory trees. Each WebFM directory tree would have a name, description, and identifier. You could even setup permissions per role to access each WebFM directory tree.
If you were able to do that, then each content type would need to be able to specify what WebFM Trees to allow users to pick files from.
Wow, that's alot. Just food for thought. Let me know what you think?
-Glenn
#1
Are you trying to kill us?
Separate roots for content-types would be crazy - and i'm not keen on roots for OGs.
It is plausible to create a "home" area unique to each user - i'll give this some further thought.
What you need to bear in mind is that DBFM does not rely on any filesystem as such, so document roots don't actually need to exist anywhere in the actual directory tree. (cool huh?)
I'll think on this one, but it'd likely be a long time before it makes it into a release.
I have no idea what this WebFM cck stuff is you're talking about tho.
M.
#2
Sorry, since WebFM is a similar module I posted the same thing there. Please note, I have not yet tried the dbfm module, only WebFM.
Not sure if dbfm even has a cck widget, but it would be cool.
I was thinking it would be neat if there was a cck field widget that you could add to your custom content types that would allow you to use dbfm. This widget would have a setting to allow you to choose the specific file space and specific directory in that file space. Each file space can be created from an existing directory of another filespace or create a fresh new one with no folders or files.
Why are you saying I'm trying to kill you? Sorry, I hope I am not throwing out to much. I am just thinking out loud.
DBFM and WebFM are great, the only main limitation is that they allow for only one file tree or file space. Why not allow for multiple file spaces? Each file space could choose to be created from an existing dbfm directory or start out empty?
Does DBFM store documents as nodes? If so, it would be cool to tap into using the Views module to allow for presenting the uploaded documents in various ways.
DBFM users need a way to:
What are your thoughts. I know all of this sounds crazy, but maybe you could take some of these ideas and run with them.
#3
I suggest you take a look at our online demo. I think WebFM and DBFM have become quite different to one-another.
On your points:
> Why are you saying I'm trying to kill you? Sorry, I hope I am not throwing out to much. I am just thinking out loud.
You made some good suggestions and putting them into practice will probably see the death of me... It's been one of those projects. With that said, I do really appreciate the feedback. This is one of the reasons why we chose the OSS platform for this project and it pleases us that others are taking an interest.
>publicly browse a specific directory and it's folders and files - not just the whole dbfm tree
This was possible, but is currently broken in 5.x.3.1 - You can send DBFM the path to browse.
> attach an ajax style browsable directory to a node or dbfm cck field widget
I'm not sure what you mean here. Files are not stored as nodes - apparently Drupals' Dries has strong feelings about that, so we avoided it (tho it would have made our lives easier).
> present different views of uploaded documents - such as show only pdf files, show the most downloaded files, show the files in a paged table view, show the files in a list view, etc. - Views provides all of this
Interesting, but again, they're not nodes so this doesn't work. DBFM is supposed to be merely a file-browser with a few bells and whistles. Have a look at the demo site, more specifically the online help here: http://dbfmdemo.lineageone.com/sites/all/modules/dbfm/webhelp/index.html it will give you a better idea of what DBFM is, why we made it and how it actually works.
> rss feeds for uploaded files, for each addition/update on a directory files, each update on a file. - could be provided by views
I'm not sure what purpose this would serve.
Thanks!
M.