Link to a specific webfm subdirectory
| Project: | Web File Manager |
| Version: | 6.x-2.10-rc4 |
| Component: | User interface |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
General: Using Drupal 6.x for higher education/library consortium. Have hundred of documents to provide. Webfm set up and working fine from all appearances.
Question: Is it possible to link directly to a subdirectory of my file structure from a specific node and present that subdir within the webfm interface?
Background: I have a documentation portal currently running on a node/book format. I want to be able to link to the webfm subdirectory where we will provide all of the vendor documentation for support and reference. the path would be siteaddress/webfm/Directors/Librarians/Docs
In the webfm interface, if I type the full url path, it continues to show the full hierarchy and does not just link to the directory I'd like to point to. I have roles & permissions set accordingly, and have done a bunch of research on this.
I imagine that this is not possible due to the way that webfm works, but it would be nice to be able to do this so I could create pages/nodes/books that point directly to a specific directory within the webfm interface without the user having to know that they will need to browse to that directory to find what they need.
I know I can just attach the individual docs to that page, but that is what we have BEEN doing and I want the browsable functionality inherent in webfm so the user doesn't have to guess which directory the document is in like they do currently.
What am I missing/misunderstanding?
Your help and knowledge sharing is greatly appreciated. Thank you for your time and effort.
#1
I am about to add an example custom module that does something similar to what you want. It programmatically creates a list of files from a specified directory and can be easily modified to add any markup. A nice feature is the inherent webfm security.
#2
That would be great. Thank you.
#3
If anyone else has any suggestions I would be very thankful to hear them.
#4
+1
#5
Is the custom module mentioned in #1 available at a different location?
#6
No. It is packaged with the latest release inside the modules directory. The info file requires renaming to make it visible. It works out of the box but is really meant as guide for custom module development.