I just installed the Web File Manager module in our brand new intranet. Everything seems to be working fine, but I am missing a major feature (major to me that is).

After uploading a file, I can attach it to a node, where it is available as ../webfm_send/xx. So far so good. When I want to upload a new revision of the same file however, I don't see any way to replace the existing version with a new one, making the newest version available at the same URL.

As things are now, I would have to upload the new revision and then go back to every node that had the original file attached and change the attached file into the new one at ../webfm_send/xy.

Are there any plans to allow for replacing already uploaded files with a newer revision, or would I be better of using some other module?

Comments

robmilne’s picture

robmilne commented

That feature doesn't exist in webfm but it is a marvelous suggestion. Currently newly uploaded files that have the same name as an existing file in the directory they are uploaded to are munged according to the functionality inside file.inc (drupal core). It might be better to offer what you suggest whereby the user has the option of replacing the file and thus inheriting the fid and thus not disturbing the attachments. I'll give this some thought but no promise of quick action since the inline upload is borrowed from the upload module which is structured for the usual flat filesystem architecture (munge ALWAYS - no option to replace). It would be relatively easy to incorporate this feature into drag-and-drop moves from the ftp staging area. I could open the ftp area to the inline upload and then one could have both upload methods with the replace option. That or I terf file.inc and make my own functions for the inline upload.

tcblack’s picture

tcblack commented
Version: 4.7.x-1.5 » 5.x-1.5

I opened and just closed a duplicate request for version 5

robmilne’s picture

robmilne commented

It is still my intention to dispense with drupal's file.inc but I don't intend on doing it in the very near future (I'm just too busy). Doing so will permit versioning, but more important for me, it will allow the files to be stored outside of web root and hence increase file security.

robmilne’s picture

robmilne commented
Title: Revisions » Work Around
Status: Active » Fixed

Since ../webfm_send/xxx paths can be aliased via the path module the same way as nodes it is possible to simply substitute the new webfm_send path for the alias. Try it - It works.

robmilne’s picture

robmilne commented
Title: Work Around » Revision Work Around
Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)