I have an old 4.7 site where I used disknode to manage download-files.
There where some open issues:
- the files (setup-files, docu and others) change quite offen, for this reason it would be nice to have some automation processes. Currently I have to delete the file and reassign it again. Otherwise if the size of the file change the downloaded file is corrupt

How can I manage files and updates using media-mover, could this be my solution?

Comments

arthurf’s picture

arthurf commented
Status: Active » Postponed (maintainer needs more info)

Hi-

I'm sorry to say, but there is no longer any 4.7 support. If you were on 5+, it sounds like media mover could help you, but I'd need to know more of the specifics.

good luck

a

stoltoguzzi’s picture

stoltoguzzi commented
Status: Postponed (maintainer needs more info) » Active

I know there is no more support for disknode, was just to describe how I have done it until now.
I would use the standard-upload or any other modules available on 6.x

some examples:

Node1 has attached/assigned files
- file1
- file2

This files are stored somewhere unter sites/default/fiels....
Now in our company this files change quit offen and I would like to update them on the webserver without many interaction.
My target would be to upload it by using an automated ftp-process an on the web-server there is a cron-job loading this file
to the right place and doing everything what is needed so that the files can be downloaded again.

I can not just overwrite them on the webserver (so far my experience) because if the file-size changes the download will not work.

arthurf’s picture

arthurf commented

The issue of doing this via FTP is that you need to 1) make sure the harvested ftp file is unique 2) match the harvested file against the current one. The problem is that drupal is going to rename these files if there is already an existing one, so you'd actually need to delete the existing file first so that the file names are kept consistent. The workflow would be something like this:

1) get ftp list of files
2) match these files against the current upload/node table
3) attach the node data to the media mover file
4) process - bypass
5) storage- use the attached node id to remove the current file
6) attach the media mover file to the node.

I think that should do it. Basically it means doing a quick rewrite of the ftp harvest and the node save operation, but neither of those should be hard. I think some of this could actually be integrated back to media mover.